Reporter Client not intended for production use for Access Log Uploads
The Reporter client was a proof-of-concept that was not intended for long-term production use. It utilizes a proprietary TCP streaming protocol which only works with Reporter 9.5.x and only if you are doing streaming logs. This does not work with Reporter 10.x which means this protocol will EOL with the support of Reporter 9.5.x in May 2019.
This feature was originally designed to quickly demo Reporter. Using this protocol and method on Reporter, Reporter streams the data, but never stores it to disk. This meant that if Reporter suffered a catastrophic failure, there was no data backup for recovery.
This feature was not designed with any ability to diagnose or troubleshoot it's behavior. If it fails, there is virtually no way to understand the failure or ensure it does not recur. Effectively, Symantec cannot analyze or troubleshoot stability with this feature in it's current design.
If the ProxySG appliance is pointed at Reporter, the most you can ensure is that the IP addresses are accurate, that the units can reach each other, and that the port the proxy is using is open for use on the server Reporter is running on.
FTP is the recommended option for production use; see Symantec Knowledge Base article Configuring access logging on the ProxySG to an FTP server and to Reporter.
Alternatively, use a method such as FTP/HTTP/Syslog.