Jessamyn (3:00:04 PM):Hello Charles Cunningham! Welcome to Liquid Web. My name is Jessamyn. How can I help you today? Me (3:00:47 PM):I am struggling to get out payments page website back up after it "stopped working" at 3:54 (our time UTC) Me (3:01:22 PM):The test URL I aam using is https://t-m.org.uk/phpsysinfo.php Jessamyn (3:01:33 PM):looking Me (3:03:39 PM):Ebven this one fails: https://t-m.org.uk/helloworld.html Jessamyn (3:08:00 PM):The site keeps trying to redirect to https, but all of your links in .htaccess look like http redirects, I tried to comment out this redirect to https that was in there: #RewriteEngine On #Options +FollowSymlinks #RewriteCond %{SERVER_PORT} 80 #RewriteRule ^(.*)$ https://t-m.org.uk/$1 [R=301,L] But it's still trying, is your database site and homeurl set at https also? I think you need to just get all your redirects to either go http or https, they look like they are conflicting and causing redirect loops Me (3:10:04 PM):Note really sure what you mean by that"But it's still trying, is your database site and homeurl set at https also?" Jessamyn (3:10:57 PM):Oh I meant that after commenting out the https redirect I found in your .htaccess, the site was still trying to go to https so there must be another redirect somewhere, like in your database, there are two rows called site and homeurl that may be going to https Me (3:11:16 PM):this is not a wordpress site. Jessamyn (3:11:24 PM):Right it looks like joomla Me (3:11:44 PM):Nope - raw php and html using a local MySQL DB Jessamyn (3:11:46 PM):Ok Me (3:12:37 PM):The .htaccess is repeated at the /web level. where should it be? Jessamyn (3:13:37 PM):It gets put in content folder Me (3:13:55 PM):ok, I'll dfelete the one at /web level... Me (3:15:00 PM):still bet "The page isn't redirecting properly" although not lotso f repeated "/contents" now Me (3:18:04 PM):Only got .htaccess in content directory now. Still same error though Jessamyn (3:18:51 PM):Ok now I commented out the https redirect in .htaccess again and now the redirect loop stopped, it's showing Forbidden error for me, I'm not seeing that you have an index page, that might be why Me (3:20:43 PM):the actually URL I'm trying to get back working is this https://t-m.org.uk/payments2018/ Seems to work now - but without the https redirect in the .htaccess. Why did that change last night? Have you updated the webserver (apache) perhaps? Or soething else which now forces https? Jessamyn (3:22:06 PM):I'm not sure, we haven't changed anything on servers especially since it's holidays Was your ssl installed recently? Me (3:22:08 PM):However now when I use on of the redirects i nthe .htaccess file such as https://t-m.org.uk/payments it redirect to an http connection which is NOT what I want Me (3:22:29 PM):Had SSL for about 6-9 months.. Jessamyn (3:23:28 PM):I'm not sure, the redirects in the .htaccess look like they are just conflicting, you would just need to update it so everything will redirect to https Me (3:24:15 PM):I still can't understand why it changed last night at 3 i n the morning!! Me (3:25:03 PM):The importnat redirects are these: Redirect 301 /payments /Payments Redirect 301 /payment /Payments Redirect 301 /Payment /Payments Jessamyn (3:25:18 PM):There were no incidents reported for last night https://status.websitesettings.com/ Your IP is slightly off maybe that could have something to do? It's pointing here: 184.106.55.126 https://www.whatsmydns.net/#A/t-m.org.uk But looks like it should be 184.106.55.132 https://cloudsites.liquidweb.com/website/361621/210034#website_details Me (3:25:58 PM):aha - is thati n the DNS? Jessamyn (3:26:43 PM):Yeah that would be your A record, or you can use the new Domain Name Alias feature instead of an A record: https://help.liquidweb.com/s/article/Using-ALIAS-DNS-Records-For-Domains-in-Cloud-Sites Jessamyn (3:27:18 PM):Or, well nevermind it looks like your DNS is with Rackspace, I'm not sure if they support that feature Me (3:28:58 PM):DNS is actually with 123reg - and the A record is pointing here|: 184.106.55.29 Me (3:29:25 PM):Shall I change it to 184.106.55.132? Jessamyn (3:29:49 PM):For t-m.org.uk? Was that changed recently? It looks like it is still pointing to Rackspace name servers: https://www.whatsmydns.net/#NS/t-m.org.uk And 184.106.55.126 https://www.whatsmydns.net/#A/t-m.org.uk Me (3:30:16 PM):oh could be - yes the nameservers are not with 123reg. Me (3:30:25 PM):Hang on I'll log in to Rackspace... Me (3:33:22 PM):I can;t seem to find a rackspace account to use - I thought you guys took it over?? Jessamyn (3:34:32 PM):We bought the Cloud Sites product from Rackspace, but dns stayed with them unless customer's manually updated it to someplace else, because we wouldn't have access to anyone's dns unless their name servers pointed to us Jessamyn (3:35:31 PM):Let me try moving your https redirect to the top of the file instead and see if that'll let it work one moment Me (3:36:01 PM):ok, thanks - although clearly the Ip address ought to be correct - I suspect that is what has changed. Me (3:39:24 PM):aha - I can see that seems to be working... Jessamyn (3:39:33 PM):Ok, it looks like just that https code in general you had in there is what was causing the issue. I completely commented out that other code you had: #RewriteEngine On #Options +FollowSymlinks #RewriteCond %{SERVER_PORT} 80 #RewriteRule ^(.*)$ https://t-m.org.uk/$1 [R=301,L] And put the code we normally use to redirect to https: https://help.liquidweb.com/s/article/Forcing-a-Secure-Connection-SSL-Using-htaccess-in-Cloud-Sites #Force SSL on entire site RewriteEngine On RewriteBase / RewriteCond %{ENV:HTTPS} !on [NC] RewriteRule ^(.*)$ https://t-m.org.uk/$1 [R,L] Jessamyn (3:39:40 PM):And now your link works Me (3:41:52 PM):Great - I can confirm it works from here as well. Many thanks. Something must have changed. Pity it meant I had to sort it out on Xmas Eve!! Hope you have a Happy Christmas if that applies to you!! Thanks for your help anyway... Jessamyn (3:41:58 PM):thanks you too