Are you getting SSL errors in your pt3agent.*.log file(s)?
Are you seeing errors like these?
2023/08/29 13:34:11.673-05:00 post2portal: serverioact 1 records, 2 lines, length= 355
2023/08/29 13:34:11.770-05:00 9318 Secure Socket Layer (SSL) failure. error code 17424: SSL routines (9318)
2023/08/29 13:34:11.771-05:00 9407 Connection failure for host protop.fdm4.com port 443 transport TCP. (9407)
2023/08/29 13:34:11.771-05:00 newSocket: Connection to HTTP server: protop.fdm4.com port 443 is unavailable. -ssl -nohostverify -clientConnectTimeout 500
2023/08/29 13:34:11.771-05:00 postURL ERROR
If so, your pt3agent is using the wrong SSL protocol and/or cipher for the portal.
Resolution
Specify the correct SSL protocol and cipher(s) the remote site requires.
NOTE: Your version of OpenEdge must support TLS1.2 and above to communicate with the ProTop Portal securely.
1. To get the protocol and ciphers, run $DLC/bin/proenv and then run:
sslc s_client -connect <domain name>:<port>
Example:
sslc s_client -connect dashboard.wss.com:443
2. In the sslc output, look for the entries Protocol and Cipher:
...
SSL-Session:
Protocol : TLSv1.2
Cipher : ECDHE-RSA-AES256-GCM-SHA384
...
3. Add these to the PORTALOPTIONS environment variable in $PROTOP/bin/localenv. (If localenv does not exist, copy it from bin/localenv.x). The PORTALOPTIONS line should look something like this:
...
export PORTALPORT=443
export PORTALOPTIONS='-ssl -nohostverify -sslprotocols TLSv1.2 -sslciphers ECDHE-RSA-AES256-GCM-SHA384'
...
4. Restart protop by deleting $PROTOP/tmp/*.flg and then running $PROTOP/bin/dbmonitor.sh. Or, let the dbmonitor service restart it.
5. Verify that data is now flowing to the portal.
Sources:
- Unable to connect ABL client to consume third-party WebServices
- How to set Client SSL Protocols and Cyphers in OpenEdge