mlebo1027
Forum Replies Created
-
I wanted to follow-up with you. After further testing, we discovered the www. variation of the link was producing a 403 server error. We made some changes to our CDN to accommodate this and replaced any instances of the www. link where we shared the form. So I think we are in good shape now.
Thank you for your reply. I didn’t necessarily think it was the case that it was your plugin but figured I’d ask to try to eliminate possible trouble spots.
I may have figured out the issue, but not sure. Some of the links to the form in question had https://www. as the prefix instead of just https://.
I sent a user reporting the issue the direct link and it worked, but I’m not convinced that is the problem.
But thank you for clarifying that it could be a server or cache issue.
Thanks for your reply. That makes sense about the bridge. When you say debug mode, do you mean debug mode in Easy WP SMTP?
Unfortunately, I am having a tremendously hard time replicating the error which makes it near impossible to troubleshoot.
I wanted to follow-up. It was an issue with that plugin. The developer made a change and we should be good to go now.
Hi @mbrsolution ,
Our hosting is with inMotion, but our mailbox is managed on our secondary domain with Network Solutions.
As for the plugin, that’s a good point. I have to do some more tests, but I think it may be using the Piotnet Pafe Conditional forms. I reached out to them as well to see if I did something wrong or if they need to address an issue on their side.
I am seeing this across multiple forms as well.