EEVblog Electronics Community Forum
EEVblog => EEVblog Specific => Topic started by: adam1213 on September 16, 2016, 02:03:31 pm
-
Presently most links on the site give a forbidden error (the root page works though)
- https://www.eevblog.com/blog/ (https://www.eevblog.com/blog/)
- https://www.eevblog.com/episodes/ (https://www.eevblog.com/episodes/)
Forbidden
You don't have permission to access /blog/ on this server.
Server unable to read htaccess file, denying access to be safe
Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request.
Apache Server at www.eevblog.com (http://www.eevblog.com) Port 443
-
http:// works, https:// doesn't. Wouldn't it accidentally have anything to do with the latest http/https discussion?
-
Lots of stuff is broken right now: the shop pages, images, links. I went there today to look up the BM235 and download the manual and got "forbidden" everywhere. This creates a terrible customer first impression. It really, really needs fixing pronto.
-
Yes it's a https upgrade thing. It's disabled so should work fine now.
-
Anyone having website access issues (not just https related) in the last 3 hours?
I'm getting a ton of errors from Pingdom
And this has been happening on and off for weeks now.
(http://i.imgur.com/hf5mG4C.png)
-
Yes.
Every time I made a post earlier it hung loading the page afterwards.
-
Every time I made a post earlier it hung loading the page afterwards.
Same. Just in the last 30 minutes. Things, like fetching preview/posting a reply, are also generally slower too compared to a few days ago. Sometimes the two just timeout and I'm not using https either.
-
I am experiencing no issues with either http or https :-//
-
Just got onto Hostgator support and they were useless.
All they could come up with was "have you optimised your wordpress site?" ::)
http://support.hostgator.com/articles/how-to-optimize-a-wordpress-installation (http://support.hostgator.com/articles/how-to-optimize-a-wordpress-installation)
-
Yeah, I've ditched Hostgator years ago and moved onto VentraIP (https://ventraip.com.au/). Their tech support and ticketing system is pretty decent. They are Australian based, too!
-
I look after a website as well ... and after some asking around, I also recommended VentraIP. Yes, they are Australian based - and we selected a Sydney based server. Both the site owner and myself were happy to support an Aussie concern and I can honestly say I've not had any problems that made me even contemplate moving elsewhere.
-
Matters when it comes to quality of service, interacting with technical support and their ability to resolve technical issues. You might take a lot of precautions by playing around with the localhost version of the site, but something always will go wrong on the live site eventually. Also, some things must be done on the actual web host directly, such as setting up domain certificates.
-
There seems to be a serious problem with https, I'm not sure why, many pages are not working :scared:
-
I've had a lot of posts hang recently. Data always goes through. If I'm impatient, I open a new window to the thread, and find my post already there successfully (even though the post-submit window is still spinning).
(The reason behind this is, something about HTTP-POST data being prioritized and uncached, so it reaches the server. Even though the accompanying HTTP-GET for the message thread might hang. Or maybe that's only for the really fancy systems that do have caching and multiple servers and stuff. I don't know if that's the case here.)
Tim
-
I'm pretty sure this whole thing is cloudflare related now.
I'm also getting a ton of server down messages from two monitoring services I use. Hostgator insist it's a cloudflare problem, and gnif I think agreed with this a few weeks back. These reports started for me a few month back, but the last few days have gotten really bad. Seems to be DNS related, which is hosted by Cloudflare.
-
maybe U got h-ILLary's dodgy server :-DD or most likely hit by Russian vs USA Cyber-warfare :box: CloudFlare maybe under attack?
-
Seems to be DNS related, which is hosted by Cloudflare.
Yeah, the past few weeks I've found that I often cannot resolve the domain name www.eevblog.com (http://www.eevblog.com) when I try to visit the site.
A manual lookup will just throw a domain not found instead of finding the usual 104.31.74.133 and 104.31.75.133. I run my own local DNS resolvers directly from the root servers so I'm not relying on any upstream provider.
Try again moments or hours later, it may work, then try again later after it has expired from the local caches again and often - boom; can't resolve again, etc... Seems to be very unreliable... up and down like the tide. :)
-
Dave's two name servers are both run by cloudflare, so try the following and let us know
Unix:
# dig @jake.ns.cloudflare.com. www.eevblog.com (http://www.eevblog.com). A
# dig @erin.ns.cloudflare.com. www.eevblog.com (http://www.eevblog.com). A
'doze:
> nslookup www.eevblog.com (http://www.eevblog.com). jake.ns.cloudflare.com.
> nslookup www.eevblog.com (http://www.eevblog.com). erin.ns.cloudflare.com.
That should bypass your local DNS resolver so see if the nameservers are returning the correct info.
-
That should bypass your local DNS resolver so see if the nameservers are returning the correct info.
Well, for me, as I said before:
A manual lookup will just throw a domain not found instead of finding the usual 104.31.74.133 and 104.31.75.133.
It is currently working so I can't post the output of a failure, otherwise I would have... :)
When it fails, it is NOT returning a response at all, as if the domain doesn't exist.... like for dig you see the QUESTION section but no ANSWER... probably status: REFUSED but I can't recall... Like I said, it's currently working right now, so I can't post a failed result... LOL