Well, now several of my websites have gone down at Exact Host. I’m guessing it’s a DNS problem, but I’m waiting to hear back from their support. Anyone else had this issue?
Yes here too, getting a https://www.capenews.com/403.shtml
My sites are getting the same 403.shtml error as well.
1 Like
I will report back here when I hear something from the hosting company.
https://www.capenews.com working at 21:12
Yes, looks like they resolved the issue. Here is what they sent me in the email for the resolution.
“ I adjusted some redirect code scripting at the top, and this allowed your site to resolve again, it seems this problem was due to Nginx being installed previously on the server, that was removed on Sunday morning on Mercury and was responsible for the redirect error.”
My recommendation would be to submit a ticket so they can look at websites that are not working and fix your .htaccess file.
1 Like
I had the same issue & it was resolved in less than 30 minutes from the time I opened a ticket.
Thank you for the post, I did not know my sites were down.
1 Like
I don’t think my sites were down, but I use Matomo analytics, which they broke as of yesterday. Exact did respond to my support ticket, they thought it was their removal of Nginx, and tried some htaccess file stuff. However, so far they have not fixed it. Anyone else on Exact hosting experiencing Matomo being broken?
1 Like
Yes, same here with Matomo being broken on several sites. I’ve sent in a ticket, but so far just the initial reply from Exact.
I’m happy to help anyone move over to BetterSiteHost if you would like something new.
1 Like
Got this from Exact this morning and it appears that they have fixed the problem affecting Matomo:
Thank you so much for your patience. We have removed Mod_evade on the server and this may help with the issue you are seeing. Can you let me know if you are still running into any issues.
1 Like
Yes, my Matomo analytics is working again. There was a bit of back and forth with Exact support, but they finally figured it out. I got basically the same answer as you Thang:
We removed Mod_Evasive from the Apache Config and this now appears to be working.
2 Likes