I heard back from SiteGround and they are asking this when these new ranges will be IN USE (ie, the crossover windows between the old IP and these new ranges)
Also they have asked as I suspected if the range can be more restrictive if possible. They did not say no but they are concerned about the size of the two /24 ranges.
Plugin Author
RexAK
(@rexak)
Hi @ccolotti
I am getting ready to contact SiteGround as well, to ask the same, since I host several sites with them.
CardConnect should have sent you an email about this change, as I think they sent the same email to all merchant account holders. I would ask that you reach out to CardConnect with your merchant number in hand, and let them know how this affects you. I’m reaching out to them today, as well, to ask if there can be some restriction on the IP address needed for the plugin to work.
CardConnect does have some testing dates, which you can get from their support channels. As of right now, I can only confirm the hard date of the switch, May 29th.
Plugin Author
RexAK
(@rexak)
Marking as resolved. If CardConnect gets back to us about possibly changing the range requirement, I’ll update this thread.
For further info about this change, please contact CardConnect support.
Oddly I never got an email from them I only saw this in the plugin..I will ask them as well, but if you find out first please share the new IP ranges via the plugin.
Guess thankfully you put the note in as there is no record of an email from them :/
-
This reply was modified 7 years, 2 months ago by
ccolotti.
They did not push back a lot, but as an IT person myself, those are two full subnets they are asking to allow.
Plugin Author
RexAK
(@rexak)
@ccolotti
I certainly will. I’ll update both you, and the plugin if a change happens. Thanks for your understanding.
Plugin Author
RexAK
(@rexak)
@ccolotti
Yes, same here, previous IT guy. I have a request in with CardConnect to see what can be done.
Can we leave this open for now then? So other people can track it? Opening a ticket with them as well.
and THANK YOU for putting the note in the plugin seeing as they are not actually emailing merchants about this change!
-
This reply was modified 7 years, 2 months ago by ccolotti.
here is CardConnect’s reply. I added to my SiteGround ticket the link and the FQDN note:
———————–
We are very sorry that you did not get the marketing email! All points in the email are covered in the following link: https://support.cardconnect.com/bolt/network-whitelisting#cardPointe-ip-update
There will be some testing dates starting in late April, which are covered at the bottom of the page, and we will be pinging servers to make sure the changes have been made by our merchants.
As for the number of IPs, we advise referencing the FQDN, which will contain the /24 blocks for both IPs to alleviate you needing to whitelist every single address individually.
Please let us know if any issues are encountered in setting up!
Thank You,
Justin
—————————————————-
-
This reply was modified 7 years, 2 months ago by ccolotti.
Plugin Author
RexAK
(@rexak)
@ccolotti
Thanks for the link. I’ll reference this link in the next plugin update coming next week, to inform other users. I’ve got a call in with them for next week and we’ll see if we can get more info regarding the IP question.
I’ve marked the thread as unresolved, so we can keep up the conversation and open it to others, if needed.
SiteGround confirmed FQDN whitelist is doable, but we need to know exactly the FQDN the plugin needs, so if you get that it would help 🙂 I THINK it’s fts.cardconnect.com but rather get confirmation from you as well as the sandbox FQDN we need that too.
-
This reply was modified 7 years, 2 months ago by ccolotti.
-
This reply was modified 7 years, 2 months ago by ccolotti.
Plugin Author
RexAK
(@rexak)
@ccolotti
Thanks for doing the research with SiteGround! The FQDN for you would be whatever CC sent you in your merchant package, but for most people using WP, you’re right, it would be “fts.cardconnect.com.”
If the FQDN whitelisting does work with SG – and they do not need to specifically open 2 range sets, then hopefully other hosting outfits can do the same. I’ll follow up with a SG ticket of my own to confirm.
Appreciate the assistance, again.
I am having SiteGround update my whitelist to
fts.cardconnect.com:8443 (production)
fts.cardconnect.com:6443 (sandbox)
In fact an NSLOOKUP of that current resolves to the current whitelisted IP 69.164.93.9. So, I suspect if we change my whitelist to the two FQDN:Ports above nothing further will need to be done when they change IP’s
I’m not sure if I’m supposed to open my own ticket or not. Sounds like this ticket was being left open so others could report about their questions about this request.
WP Engine definitely doesn’t want to open those 2 range sets. It’s a shared server, so that’s a big ask.
What specifically do we need to ask our web hosts that will ensure CardConnect works after 5/29?
@askwpgirl
See if your host can whitelist just the FQDN versions not the IP ranges.
fts.cardconnect.com:8443 (production)
fts.cardconnect.com:6443 (sandbox)
