ShipStation and Firewall
-
I could only find one reference to ShipStation in the forum, but the issue was never fixed. ShipStation worked fine on the staging site, I suspect because WF was in learning mode. The Issue, on the live site: ShipStation receives order information from WooCommerce, but WooCommerce does not receive information from ShipStation. Thus,
- Users get only the price option, in this case FedEX, provided by WooCommerce and not multiple options provided by ShipStation
- WordPress Admins never see the order status change from its initial setting, in this case ‘Processing’ when it is changed in ShipStation
- The ShipStation account holder sees an error in their ShipStation order grid when they update the shipping status on the ShipStation site. This is the action that results in 2.
I put WordFence back into learning mode – that hasn’t helped after a day.
ShipStation support did give me a list of eight IP addresses with the CIDR notation (e.g. like: 34.200.1.155/32) with the caveat that they change frequently so may not be good for long. I installed them all in WF – that didn’t help. Maybe WF doesn’t like the CIDR? I took that off – didn’t help.
The web logs revealed that ShipStation is using RestSharp/106.3.1.0 as its user agent. In theory I should be able go to Wordfence > Firewall > Manage Firewall and the ‘Allowlisted URLs’ section and enter shipstation.com, Param Type: POST body, and the Param Name. I tried RestSharp/106.3.1.0 as the param name so that generates: request.body[RestSharp/106.3.1.0] for the parameter. That looks like it should work, but it doesn’t.
I purged the server side cache and also disabled it – that didn’t help.
No other firewalls on the system.
I’m out of ideas, can anyone help?
- The topic ‘ShipStation and Firewall’ is closed to new replies.