Also @rg305 I checked Google and the website seems to be okay?
1 Like
Go figure, only one vendor has it listed - and that's one that I use:
VirusTotal - URL - b0b04a3fa0b9c303736d546d0bcbdd2d3cd789f333af96d8fd81117b9700c47f
9 Likes
Okay, well if there is a security issue I would love to fix it, just as I'm still trying to fix this certificate issue! I have submitted a review request to Fortiguard.
1 Like
Thanks @MikeMcQ I have contacted them and I will get back to you if it solves the problem. Much appreciated!
3 Likes
@rg305 and we're clean! phew!
3 Likes
@nanana Send your network team the two URL requests in post #22
It shows the URL for your test file works with a default user agent. It has http response 200 and note the Server: nginx header.
Yet, the identical request using a user-agent the same as Let's Encrypt server uses fails with a 503. More importantly, there is no Server response header which often indicates it never reached your server. Also, the existence of the P3P response header points even further to a firewall device.
In any event, show that post to your network team so they can reproduce the error and fix it. If they can't they should contact Palo Alto Networks or that vendor you mentioned in the other thread with the dynamic filtering data.
8 Likes
Thank you so much!
I did as you suggest, and they responded with:
I have allowed acme-protocol inbound traffic on the DC firewall, which I can see some blocking on the DC Palo
I ran certbot again, and voila! Success.
That was a tricky one. I really appreciate the help @MikeMcQ and @rg305 !
3 Likes
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.