Otdfbt

Is an up-to-date browser secure on an out-of-date OS?

Did 3000BC Egyptians use meteoric iron weapons?

The difference between dialogue marks

Have you ever entered Singapore using a different passport or name?

How to type this arrow in math mode?

Falsification in Math vs Science

What is the motivation for a law requiring 2 parties to consent for recording a conversation

What do the Banks children have against barley water?

Does a dangling wire really electrocute me if I'm standing in water?

Can someone be penalized for an "unlawful" act if no penalty is specified?

Is flight data recorder erased after every flight?

Why did Acorn's A3000 have red function keys?

What to do when moving next to a bird sanctuary with a loosely-domesticated cat?

Can a rogue use sneak attack with weapons that have the thrown property even if they are not thrown?

What is the closest word meaning "respect for time / mindful"

If a Druid sees an animal’s corpse, can they wild shape into that animal?

For what reasons would an animal species NOT cross a *horizontal* land bridge?

Right tool to dig six foot holes?

Shouldn't "much" here be used instead of "more"?

Can we generate random numbers using irrational numbers like π and e?

Why hard-Brexiteers don't insist on a hard border to prevent illegal immigration after Brexit?

How to deal with fear of taking dependencies

Pokemon Turn Based battle (Python)

Can you compress metal and what would be the consequences?

Nginx reverse proxy domain root location redirects back to server IP

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;

0

I have a client with an existing domain name which cannot be pointed to my server just yet.

So in the meanwhile I've added my node app and configuring the reverse proxy. This is what I've done:

1) Added domain entries to my local machine's hosts file:

134.209.53.229 example.com
134.209.53.229 www.example.com

2)on my server hosts file, I did the same:

134.209.53.229 example.com
134.209.53.229 www.example.com

3) My nginx reverse proxy setup. This is my /etc/nginx/sites-available/default file:

server 
 listen 80 default_server;
 listen [::]:80 default_server;

 root /var/www/html;
 index index.php index.js index.html index.htm index.nginx-debian.html;

 server_name example.com www.example.com;

 location / 
 proxy_pass http://localhost:8000;
 proxy_http_version 1.1;
 proxy_set_header Upgrade $http_upgrade;
 proxy_set_header Connection 'upgrade';
 proxy_set_header Host $host;
 proxy_cache_bypass $http_upgrade;
 

Now what happens if I visit any subpath, like http://example.com/products, everything works fine.

But, when I visit root http://example.com - contents are served as expected, but the address in my browser address bar changes to http://134.209.53.229 .

Looking at devtools network tab, I see that initiator is example.com, but in the request headers host is actually 134.209.53.229 (not example.com).

Is any of what I've done above causing this? Or should I be digging up my app? So far I'm not finding any cause inside the app.

EDIT: it appears that this only happens in google chrome. Is this expected behavior from chrome?

nginx reverse-proxy

share|improve this question

edited Apr 6 at 20:15

geochanto

asked Apr 6 at 20:07

geochantogeochanto

992

New contributor

geochanto is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  There's nothing in the nginx configuration to cause this. You should keep looking at your app.
  
  – Michael Hampton♦
  Apr 6 at 20:13
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @MichaelHampton I just noticed that it only happens on google chrome. Other browsers are fine. I have no SSL set up, I'm thinking it could have something to do with it maybe.
  
  – geochanto
  Apr 6 at 20:14
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Did you clear your browser cache?
  
  – Michael Hampton♦
  Apr 6 at 20:42
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @MichaelHampton yes. The strange thing is that it ONLY happens in incognito mode lol. I guess it's not much of a problem after all.
  
  – geochanto
  Apr 6 at 20:50
  

  
  
  
  

add a comment | 

0

I have a client with an existing domain name which cannot be pointed to my server just yet.

So in the meanwhile I've added my node app and configuring the reverse proxy. This is what I've done:

1) Added domain entries to my local machine's hosts file:

134.209.53.229 example.com
134.209.53.229 www.example.com

2)on my server hosts file, I did the same:

134.209.53.229 example.com
134.209.53.229 www.example.com

3) My nginx reverse proxy setup. This is my /etc/nginx/sites-available/default file:

server 
 listen 80 default_server;
 listen [::]:80 default_server;

 root /var/www/html;
 index index.php index.js index.html index.htm index.nginx-debian.html;

 server_name example.com www.example.com;

 location / 
 proxy_pass http://localhost:8000;
 proxy_http_version 1.1;
 proxy_set_header Upgrade $http_upgrade;
 proxy_set_header Connection 'upgrade';
 proxy_set_header Host $host;
 proxy_cache_bypass $http_upgrade;
 

Now what happens if I visit any subpath, like http://example.com/products, everything works fine.

But, when I visit root http://example.com - contents are served as expected, but the address in my browser address bar changes to http://134.209.53.229 .

Looking at devtools network tab, I see that initiator is example.com, but in the request headers host is actually 134.209.53.229 (not example.com).

Is any of what I've done above causing this? Or should I be digging up my app? So far I'm not finding any cause inside the app.

EDIT: it appears that this only happens in google chrome. Is this expected behavior from chrome?

nginx reverse-proxy

share|improve this question

edited Apr 6 at 20:15

geochanto

asked Apr 6 at 20:07

geochantogeochanto

992

New contributor

geochanto is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  There's nothing in the nginx configuration to cause this. You should keep looking at your app.
  
  – Michael Hampton♦
  Apr 6 at 20:13
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @MichaelHampton I just noticed that it only happens on google chrome. Other browsers are fine. I have no SSL set up, I'm thinking it could have something to do with it maybe.
  
  – geochanto
  Apr 6 at 20:14
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Did you clear your browser cache?
  
  – Michael Hampton♦
  Apr 6 at 20:42
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @MichaelHampton yes. The strange thing is that it ONLY happens in incognito mode lol. I guess it's not much of a problem after all.
  
  – geochanto
  Apr 6 at 20:50
  

  
  
  
  

add a comment | 

I have a client with an existing domain name which cannot be pointed to my server just yet.

So in the meanwhile I've added my node app and configuring the reverse proxy. This is what I've done:

1) Added domain entries to my local machine's hosts file:

134.209.53.229 example.com
134.209.53.229 www.example.com

2)on my server hosts file, I did the same:

134.209.53.229 example.com
134.209.53.229 www.example.com

3) My nginx reverse proxy setup. This is my /etc/nginx/sites-available/default file:

server 
 listen 80 default_server;
 listen [::]:80 default_server;

 root /var/www/html;
 index index.php index.js index.html index.htm index.nginx-debian.html;

 server_name example.com www.example.com;

 location / 
 proxy_pass http://localhost:8000;
 proxy_http_version 1.1;
 proxy_set_header Upgrade $http_upgrade;
 proxy_set_header Connection 'upgrade';
 proxy_set_header Host $host;
 proxy_cache_bypass $http_upgrade;
 

Now what happens if I visit any subpath, like http://example.com/products, everything works fine.

But, when I visit root http://example.com - contents are served as expected, but the address in my browser address bar changes to http://134.209.53.229 .

Looking at devtools network tab, I see that initiator is example.com, but in the request headers host is actually 134.209.53.229 (not example.com).

Is any of what I've done above causing this? Or should I be digging up my app? So far I'm not finding any cause inside the app.

EDIT: it appears that this only happens in google chrome. Is this expected behavior from chrome?

nginx reverse-proxy

share|improve this question

edited Apr 6 at 20:15

geochanto

asked Apr 6 at 20:07

geochantogeochanto

992

New contributor

geochanto is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

134.209.53.229 example.com
134.209.53.229 www.example.com

134.209.53.229 example.com
134.209.53.229 www.example.com

server 
 listen 80 default_server;
 listen [::]:80 default_server;

 root /var/www/html;
 index index.php index.js index.html index.htm index.nginx-debian.html;

 server_name example.com www.example.com;

 location / 
 proxy_pass http://localhost:8000;
 proxy_http_version 1.1;
 proxy_set_header Upgrade $http_upgrade;
 proxy_set_header Connection 'upgrade';
 proxy_set_header Host $host;
 proxy_cache_bypass $http_upgrade;
 

share|improve this question

edited Apr 6 at 20:15

geochanto

asked Apr 6 at 20:07

geochantogeochanto

992

New contributor

geochanto is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

share|improve this question

edited Apr 6 at 20:15

geochanto

asked Apr 6 at 20:07

geochantogeochanto

992

New contributor

geochanto is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

asked Apr 6 at 20:07

geochantogeochanto

992

New contributor

geochanto is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

asked Apr 6 at 20:07

geochantogeochanto

992