Welcome! Log In Create A New Profile

Advanced

"This page isn't working" error

Posted by Friscia, Michael 
Friscia, Michael
"This page isn't working" error
May 23, 2018 03:40PM
I wonder if anyone knows how to debug this.

I have two URLs:
Working
https://www.yalemedicine.org/doctors/marcus_bosenberg/
not working
https://www.yalemedicine.org/doctors/antonio_subtil/

From the Nginx configuration side, these go through the same identical configuration. If I go to the upstream server, both URLs work for the “non-Nginx” version of the pages.

The problem I have is that I can’t seem to get an error in the logs from Nginx since I am just getting the error “This page isn’t working” and as a result there are no useful headers or information being passed.

Any thoughts/help would be appreciated on what I need to do to get some sort of logged error from Nginx to give me a clue what is wrong with this page.

___________________________________________
Michael Friscia
Office of Communications
Yale School of Medicine
(203) 737-7932 - office
(203) 931-5381 - mobile
http://web.yale.eduhttp://web.yale.edu/

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Friscia, Michael
Re: "This page isn't working" error
May 23, 2018 04:30PM
Never mind, I had an error in a config file that was forcing a 444 response based on a regex that accidentally matched the second URL…

___________________________________________
Michael Friscia
Office of Communications
Yale School of Medicine
(203) 737-7932 - office
(203) 931-5381 - mobile
http://web.yale.eduhttp://web.yale.edu/

From: nginx <[email protected]> on behalf of Michael Friscia <[email protected]>
Reply-To: "[email protected]" <[email protected]>
Date: Wednesday, May 23, 2018 at 9:37 AM
To: "[email protected]" <[email protected]>
Subject: "This page isn't working" error

I wonder if anyone knows how to debug this.

I have two URLs:
Working
https://www.yalemedicine.org/doctors/marcus_bosenberg/https://urldefense.proofpoint.com/v2/url?u=https-3A__www.yalemedicine.org_doctors_marcus-5Fbosenberg_&d=DwMGaQ&c=cjytLXgP8ixuoHflwc-poQ&r=wvXEDjvtDPcv7AlldT5UvDx32KXBEM6um_lS023SJrs&m=wau5zNWvt_aLDp8-lgMv3rKqByJuGlCPCzZZ5G_vPK4&s=eyH5XIEuH9_GbwXJopm-oLc4vkv4xISy65lMbRZHE8Y&e=
not working
https://www.yalemedicine.org/doctors/antonio_subtil/https://urldefense.proofpoint.com/v2/url?u=https-3A__www.yalemedicine.org_doctors_antonio-5Fsubtil_&d=DwMGaQ&c=cjytLXgP8ixuoHflwc-poQ&r=wvXEDjvtDPcv7AlldT5UvDx32KXBEM6um_lS023SJrs&m=wau5zNWvt_aLDp8-lgMv3rKqByJuGlCPCzZZ5G_vPK4&s=sZDEs1sDBzxTqeqzVTcJ_7eP3JGGLLmGLRoiTqTpRI8&e=

From the Nginx configuration side, these go through the same identical configuration. If I go to the upstream server, both URLs work for the “non-Nginx” version of the pages.

The problem I have is that I can’t seem to get an error in the logs from Nginx since I am just getting the error “This page isn’t working” and as a result there are no useful headers or information being passed.

Any thoughts/help would be appreciated on what I need to do to get some sort of logged error from Nginx to give me a clue what is wrong with this page.

___________________________________________
Michael Friscia
Office of Communications
Yale School of Medicine
(203) 737-7932 - office
(203) 931-5381 - mobile
http://web.yale.eduhttp://web.yale.edu/

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Aleksandar Lazic
Re: "This page isn't working" error
May 23, 2018 04:50PM
Hi.
On 23/05/2018 13:37, Friscia, Michael wrote:
>I wonder if anyone knows how to debug this.
>
>I have two URLs:
>Working
>https://www.yalemedicine.org/doctors/marcus_bosenberg/
>not working
>https://www.yalemedicine.org/doctors/antonio_subtil/

Looks like your SDL Component does not exist for this url?

```
# curl -v https://www.yalemedicine.org/doctors/antonio_subtil/ -o lala.html

...
{ [5 bytes data]
< HTTP/1.1 404 Not Found
< Server: nginx
< Date: Wed, 23 May 2018 14:34:55 GMT
< Content-Type: text/html; charset=utf-8
< Transfer-Encoding: chunked
< Connection: keep-alive
< Cache-Control: public, max-age=3600
< Expires: Wed, 23 May 2018 15:06:17 GMT
< Last-Modified: Wed, 23 May 2018 14:06:17 GMT
< X-Secured-Page: false
< access-control-allow-origin: *
< X-ID: 5623a9b5930d9c6cc5c62fbd7d35758b
< X-Proxy: ysm-nginx-prod14
< X-ProxyKey: httpswww.yalemedicine.org/doctors/antonio_subtil/
< X-ProxyKeyAccept: httpswww.yalemedicine.org/doctors/antonio_subtil/*/*
< X-NoCache: 0 (1=bypass/0=cache delivery)
< X-UpstreamCacheStatus: STALE
< X-RemoteAddr: 195.90.20.201
< X-Origin-Forwarded-For: 195.90.20.201
<
{ [15694 bytes data]
100 33286 0 33286 0 0 8051 0 --:--:-- 0:00:04 --:--:-- 8051
* Connection #0 to host www.yalemedicine.org left intact
```

```
<!--End SiteImprove Priority Script-->
....
<!--
******************************************
* Web Application Time Zone: Eastern Standard Time
*
* SDL Page URI: tcm:990-143643-64
* Last Published: 3/22/2017 9:13:51 PM
* Filename: 404.html
* Revision Date: 1/16/2013 5:25:05 PM
* Version: 4
*
* Component Presentations:
*
* SDL Component: 404 Error Message - tcm:990-143642
* SDL Component Template: Code - tcm:990-224-32
* Model name: Code
* Revision Date: 6/21/2015 9:11:47 PM
* Version: 4
*****************************************-->
```

This is in the working one.

```
<!--End SiteImprove Priority Script-->
...
<!--
******************************************
* Web Application Time Zone: Eastern Standard Time
*
* SDL Page URI: tcm:990-259810-64
* Last Published: 10/19/2017 10:53:43 AM
* Filename: detail.html
* Revision Date: 12/1/2016 9:53:27 AM
* Version: 8
*
* Component Presentations:
```

Hth
Aleks

>From the Nginx configuration side, these go through the same identical
>configuration. If I go to the upstream server, both URLs work for the
>“non-Nginx” version of the pages.
>
>The problem I have is that I can’t seem to get an error in the logs
>from Nginx since I am just getting the error “This page isn’t working”
>and as a result there are no useful headers or information being
>passed.
>
>Any thoughts/help would be appreciated on what I need to do to get some
>sort of logged error from Nginx to give me a clue what is wrong with
>this page.
>
>___________________________________________
>Michael Friscia
>Office of Communications
>Yale School of Medicine
>(203) 737-7932 - office
>(203) 931-5381 - mobile
>http://web.yale.eduhttp://web.yale.edu/
>

>_______________________________________________
>nginx mailing list
>[email protected]
>http://mailman.nginx.org/mailman/listinfo/nginx

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Sorry, only registered users may post in this forum.

Click here to login