Anyone having issues with CRE / Credit card processing today? We’re trying to figure out the issue behind this error: “Failed to connect (EOF occurred in violation of protocol (_ssl.c:600))”
We are on 10.2.300.12
I am seeing the same error in my credit card logs.
Just seeing: Failed to connect (timed out) as the response message in credit card transaction history.
version 10.2.700.11
still troubleshooting
We’re getting the same thing… 2021.1
I think someone let their certificate expire
SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed
I have an open ticket with Epicor - this is their response
EPA Changing URLS used to send transactions to Epicor Payment Gateway Epicor 10.KB0128565
Authored by Ramiro Nunez • 28 Views • about a month ago • ()() () () ( )
[ Print](javascript:void(0))
Issue
CRE updated Updated Ip records, this can impact URLs in use.
Error
URL and Ip addresses will fail and must be replaced
Resolution
As part of an ongoing effort to optimize our payment process, we would like to inform our users of the new URLs that should be used for accessing our payment gateway. Going forward, we recommend using the following URLs:
- paygate1.eaglesoa.com
- paygate2.eaglesoa.com
- paygate3.eaglesoa.com
- paygate1n.eaglesoa.com
- paygate2n.eaglesoa.com
- paygate3n.eaglesoa.com
IP addresses associated with the new URLs:
- 13.56.35.49
- 3.212.73.50
- 34.194.218.111
- 52.38.54.206
- 52.39.222.77
- 52.8.244.96
Please make sure to whitelist these IP addresses if you have any network or firewall restrictions in place.
These URLs are fully functional and will provide our users with the best possible experience when accessing our payment gateway.
Those URLs should be replaced in the EPSaddrs.list
This is a path example: C: > ProgramData > Epicor > CRE >PaymentApp> Gateway> SRTP> CASRV > EPSaddrs.list
we would like to remind our users that the following URLs and IP addresses will no longer work and must be replaced:
- paygate-lb00-1446542609.us-east-1.elb.amazonaws.com (54.85.143.80, 54.87.127.143)
- paygate-west-1-lb00-726856062.us-west-1.elb.amazonaws.com (52.9.225.142)
- paygate-nwest-lb00-1692736888.us-west-2.elb.amazonaws.com (54.200.196.36)
We appreciate your cooperation in this matter and hope that these changes will improve your experience with our payment gateway. If you have any questions or concerns, please do not hesitate to contact our support team.
Notes
Please note that although the following URLs are still working, they are no longer preferred:
3 Likes
Thank you for posting. We have been waiting for a status update on our EpiCare case for several hours without any progress.
We followed this KB and it corrected the issue. We will update our case to reflect this and ensure that this applies to all customers and scenarios.
It worked for us as well, just one comment it was not clear where to enter the URL’s for us so ==> The URLs need to be updated in the app.cfg file which can be found in C:\Program Files (x86)\Epicor\CRE\Payment App
The IP addresses need to be changed in the EPSaddrs.list file. It is located in C: > ProgramData > Epicor > CRE >Payment App> Gateway> SRTP> CASRV > EPSaddrs.list
1 Like
Good to know! We only updated EPSaddrs.list with the IP addresses and it started working again for us. I’ll have to update the URLs in the other file as you noted just in case.
I updated the EPSaddrs.list processed a credit card and noticed the EPSaddrs.list file would be automatically updated with a new list of ip addresses.
I checked out the KB article listed above, KB0128565, and it looks like it was rewritten. It no longer references the EPSaddrs.list file only the app.cfg file.
I cleared all the ip addresses in the EPSaddrs.list file and updated the app.cfg file according to the KB article and we are able to process credit cards. The EPSaddrs.list file still updates with a new list of ip address when a credit card is processed.
I have updated the EPSaddrs.list and the config file and we still are not able to process credit cards. I tried to clear the EPSaddrs.list as well and that didn’t work either.
I did get notification from Epicor to remove the # in config file, which I did but that did not work either.
after removing the # in the config file did you add in the list of eaglesoa.com urls? and then restart the Epicor Payment App service?
https://epiccare.epicor.com/epiccare?id=epiccare_kb_article&sys_id=fa69b3891b5f61d06189fc8e034bcb48
Sure did 
Was there any resolution, our CRE credit card transactions suddenly stopped working on June 6th too. We implemented all of the above solutions, re-installed the software and we still cannot process CC’s.
Orders are piling up and Epicor still has no solution. 2021.2.12
Another odd behavior is the ability to hit the paypal test site with our pilot database but not our production database?
Ours started working again on its own so we closed the ticket out.
Did you try the other solutions on this thread?
I know a few people changed their URLs and theirs started working.
All the fixes above were for E10 only. We had an E10 app server with CC services hitting port 443 along with our E11 that we turned off and in Credit card configuration we had to remove the IP address we had been using and replace it with the localhost.
Processing backlog is the priority for now.