To fix these errors, please make sure that your domain name was entered correctly and the DNS A/AAAA record(s) for that domain contain(s) the right IP address

lucky you :slight_smile:
I’m eating cherries so I’ll survive the midnight muchies - lol
bag shows:
" I :heart: :maple_leaf: :cherries: " ™

We need to put a file in that folder to see if it is accessible or not.

@rg305 thanks for everything appreciate the kindness. I’ll continue to work on this. Get some rest bud!

2 Likes
2 Likes

will update again when there is progress

I do my best work at night
:owl:

But as you wish…
Cheers from Miami :beers:

1 Like

Ah gotta love cherries Great stuff if I could only be half as healthy as you. the WFH lifestyle getting me munching on real bad stuff haha

just created a test file

Hey cheers bud, would really want to visit Miami one day
Cheers from the island state :singapore: :beers:

2 Likes

I can’t see that file:

curl -Iki http://staging.tite.rdc.nie.edu.sg/.well-known/acme-challenge/test-file-1234
HTTP/1.1 302 Found
Cache-Control: no-cache
Content-length: 0
Location: https://staging.tite.rdc.nie.edu.sg/.well-known/acme-challenge/test-file-1234
  1. Are you sure that IP 118.201.204.72 reaches your staging server?
  2. Are there any logs to review the attempts?
2 Likes

I’m amazed what sorcery is this. Alright gonna check right this instant

On second look the HTTP is being redirected to HTTPS.

That means it is ignoring our location section…
hmm…

1 Like

This is way beyond me but does the 10.55.55.80:22 at the top help

1 Like

OK
Looking back at the code.
There is no server_name statement in the HTTP block.
That means there is another HTTP block doing the redirection.
And we need to add the server_name there.

2 Likes

Like this:

But since you only pass files via SSH, perhaps there is some code out of your reach…
Like I would run this locally:
nginx -T
We may have to introduce the location statement in the HTTPS block…

2 Likes

OK my money is on there being a “global” server-wide HTTP to HTTPS redirection (somewhere outside our vision).
Which overrides whatever we did in the HTTP block.
Easily tested - add the server_name and then we will know.

If it fails to help, then move the location block code to the HTTPS block.

1 Like

This just keeps getting weirder…
The HTTPS connections are also being redirected to HTTPS
[that’s an infinite loop]

curl -Iki https://staging.tite.rdc.nie.edu.sg/
HTTP/1.1 302 Moved Temporarily
Server: nginx/1.16.1
Date: Thu, 03 Sep 2020 05:40:00 GMT
Content-Type: text/html
Content-Length: 145
Location: https://staging.tite.rdc.nie.edu.sg/
Strict-Transport-Security: max-age=16000000; includeSubDomains; preload;
1 Like

Alright fingers crossed… also need to check if u mean this
image

1 Like

yes go with that change first

2 Likes

Oh boy… i could let the server guys know about this

1 Like

Ask the firewall guys: Which is the server that 118.201.204.72 is being NATed to?
It should match the IP of the server you are modifying.