@spiderrobotpig Did you get a certificate from Let's Encrypt?

@spiderrobotpig

Is the nginx user allowed to access the certs?

Are the permissions set correctly on that directory?

feel free to ping with any additional info, I use nginx in the majority of the servers I manage

@boots it's definitely something we missed, but we've changed all the instances we are aware of Also grep -R isn't pulling anything up

@spiderrobotpig grep -R example /etc/nginx

@boots currently out for a few minutes but we'll run it

@boots YAY THANK YOU

@boots Wait, so it old us the file, but when we open it the xample.com isn'

@spiderrobotpig nano ^W example

@spiderrobotpig (open it in nano, hit ctrl-w, search example)

@InspectorCaracal we did that though which is the confusing part

@spiderrobotpig HMM. Check that you don't have multiple nginx configuration files active?

@InspectorCaracal that might be the issue tbh. Not sure how to check that tho

@spiderrobotpig Do you know what the OS you're working on is? If it's a version of Ubunto or Debian (if you install things with apt-get) then it should be in /etc/nginx/sites-available/

@InspectorCaracal Ubuntu. And we changed that one. We'll double check tho :3

@nightpool Yah haha. But we've changed all instances we know of and grep -R isn't pulling up anything

@spiderrobotpig So are you still getting the same error? or a different one?

@nightpool same error. That's the weird part

@spiderrobotpig did you restart nginx after changing the configuration? Did you do nginx config-test to make sure you didn't forget a semicolon?

@nightpool

yes tothe first, and we're running nginx-t

@krainboltgreene Yah, the issue is that we've changed all known instances to the correct domain and grep-R isn't pulling up anything