I'm only assuming the . is reference for NGINX directory.
I don't like assumptions.
Can you place a test text file there and see if it can be reached from the Internet?
Also, there are 162 posts here...
This is vague and requires one to scroll back [way back]:
Please be more detailed in your posts [even if it sounds like you are repeating yourself - don't worry].
2 Likes
So when I turned everything off and only had the "ia.midwestrp.net" domain loading, I was able to reach the hello.txt file we created, no issues. However, now that I reverted everything back, it is no longer accessible.
So I was able to reach the test file at "ia.midwestrp.net/hello2.txt" when it was only that domain loaded.
I tore that full config apart - line by line - I can't find the problem.
2 Likes
That really should just be
location / {
The use of ~ indicates a regular expression and changes the priority of location block selection. In your case it overrides the location for the /.well-known/acme-challenge
See docs (link here)
I don't think that explains all the odd things seen here but it's one thing anyway.
5 Likes
let's see which process binds on port 80. maybe find something else
in powershell
Get-Process -Id (Get-NetTCPConnection -LocalPort 80).OwningProcess
and it's sweeping trash under the rug approch, but can it look like short downtown doesn't matter can we just kill entire nginx and run in standalone mod?
3 Likes
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.