Error visiting hompage
-
HTTP Headers info when site is down – only one record::
mypocketcookbook.wordpress.com (failed)net::ERR_SSL_PROTOCOL_ERROR document Other
Header info:
Request URL: https://mypocketcookbook.wordpress.com/
Referrer Policy: strict-origin-when-cross-origin
Provisional headers are shown
DNT: 1
sec-ch-ua: “Chromium”;v=”92″, ” Not A;Brand”;v=”99″, “Google Chrome”;v=”92″
sec-ch-ua-mobile: ?0
Upgrade-Insecure-Requests: 1
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.159 Safari/537.36 -
One more different header info:
Request URL: https://mypocketcookbook.wordpress.com/
Referrer Policy: strict-origin-when-cross-origin
cache-control: no-cache, must-revalidate, max-age=0
content-encoding: gzip
content-type: text/html; charset=UTF-8
date: Tue, 31 Aug 2021 08:42:17 GMT
expires: Wed, 11 Jan 1984 05:00:00 GMT
host-header: WordPress.com
link: <https://wp.me/cXalT>; rel=shortlink
server: nginx
vary: Accept-Encoding
x-ac: 1.hhn _dfw
x-hacker: If you’re reading this, you should visit automattic.com/jobs and apply to join the fun, mention this header.
x-robot-tag: noindex, nofollow
Provisional headers are shown
DNT: 1
Upgrade-Insecure-Requests: 1
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.159 Safari/537.36 -
Hello there,
Many thanks for all of that information.
Can you tell us your location when the site is down please?
Many thanks.
-
-
Assuming for a moment this is not an ISP issue, the next best step would be to see if you can determine if this a computer operating system issue. There are a couple of ways to test this:
1. View your site through a mobile phone. Do you encounter the same error? How about with wifi enabled, and then wifi disabled?
2. Have a friend in your location with a Mac or iPhone view your site. Do they encounter the same error?
I did discover the 107 error is common in PCs when viewing sites with SSL. I located an article which covers some possible solutions.
Lastly, I wanted to clarify that your site hasn’t been “down”. It has remained functional the entire time, however, something on your end is preventing you from accessing the site. Our hope is this helps you understand the issue better and move closer to resolving.
-
Ups..
Looks like the reason of my problem is my location..
I’ve tried to enter the site, when site is down – usually it down 3-10 minutes – via vpn (not my vpn for remote work, but common vpn like Psiphon), and every time site opens without problems.I hope you know about specific situation in our country..
Do you have any ideas please to resolve this issue? Change domain name? -
Were you able to test any of the scenarios prescribed above?
I hope you know about specific situation in our country.
We can look into this further. Can you tell us the following:
1. Has this ever happened before?
2. How long as it been working without issue, to your knowledge?
3. When exactly did this issue start?Thanks!
-
I started blog in April, and in May I note this problem. May be it happens before, but in April I’ve been not active on site.
“Site is down” means I cannot access the site from my computer.
From mobile phone I’ve also sow this message – mypocketcookbook.wordpress.com sent an invalid response.
Both in Chrome and in Samsung browser.Results, related to “Error 107 Code Problem Issue” article:
1. Firewall is on. When switched to “Off” – does not help. Proxy not used.
2. All extensions disabled – does not help.
3. Date and time: UTC+3, Minsk
4. No “word” word found in hosts file
5. Experimental QUIC Protocol disabled – does not help.
6. Internet Security level – medium
7. SSL state cleaned – does not help.
8. System Host File deleted – does not help.
9. Caches and Cookies cleaned – does not help.
10. Certificate Error ignored – does not help.
11. Chrome – last version
12. SSL state:
SSL 3.0 – Disabled
TSL 1.0 – Enabled
TSL 1.1 – Enabled
TSL 1.2 – Enabled
TSL 1.3 – Disabled
13. Antivirus deactivated – does not help.Thank you for your help!!!
-
So it seems we’ve narrowed it down to your location via VPN, but that still means it could be your ISP. I’d recommend reaching out to your ISP directly to have them look into things. Contacting them as a customer will make more progress in seeing why you’re unable to access your site URL.
Let us know what you find out!
- The topic ‘Error visiting hompage’ is closed to new replies.