Cpanel error when using redirects.

[D.B.Cooper]

I've been experiencing a strange error when attempting to add redirects using my host's cpanel. I suppose I could add them directly to the .htaccess file but I find it a bit of a schlepp digging through the various directories to edit each one by hand. Besides, I still want to know why this is happening.

Anyhow, it all worked fine up till now. I've had a word with my hosting provider and they say it works fine from their end. But for some unknown reason reason I can no longer do it. I get this error when a make an attempt:

Not Found

The server was not able to find the document (./403.shtml) you requested.
Please check the url and try again. You might also want to report this
error to your web hosting provider.

I have no idea what's causing this. Any experts on here that can lend a hand?

 

[RSkeens]

This could be caused by a number of things and most of which are server side. The only way to know the cause of the problem with certainty would be for the web host to do their job and go over the server's error logs.

 

[SilverNodashi]

I've been experiencing a strange error when attempting to add redirects using my host's cpanel. I suppose I could add them directly to the .htaccess file but I find it a bit of a schlepp digging through the various directories to edit each one by hand. Besides, I still want to know why this is happening.

Anyhow, it all worked fine up till now. I've had a word with my hosting provider and they say it works fine from their end. But for some unknown reason reason I can no longer do it. I get this error when a make an attempt:

Not Found

The server was not able to find the document (./403.shtml) you requested.
Please check the url and try again. You might also want to report this
error to your web hosting provider.

I have no idea what's causing this. Any experts on here that can lend a hand?

If they say it's working fine on their end, then chances are it might be fine. You might see a cached version of the previous / non-working redirect. If you PM me the URL (in case you don't want to advertise a website here for free) then I can see if it works or not

 

[RSkeens]

If they say it's working fine on their end, then chances are it might be fine. You might see a cached version of the previous / non-working redirect. If you PM me the URL (in case you don't want to advertise a website here for free) then I can see if it works or not

He is getting the error from cPanel itself, not the actual redirect. The error message makes that quite clear.

 

[SilverNodashi]

He is getting the error from cPanel itself, not the actual redirect. The error message makes that quite clear.

not quite. cPanel (a hosting control panel) has a facility where an end user can quickly setup a redirect, which basically creates a .htaccess file. The problem is that quite often the end user doesn't see the changes immediately since the website is caches on his PC, his ISP's transparent proxy(s), and depending the type of website (i.e. CMS / blog / forum, etc) inside the website's temp / cache folder. If the redirect is to another website, then it could be a DNS cache issue as well.

He then need to clear his cache and force a proxy refresh (can be done by pressing CTRL+F5 multiple times, or adding a "/?" to the URL). He can also test the redirect with an anonymizer proxy, like http://www.proxify.com, http://www.zend2.com/ or http://www.youhide.com/ etc.


This assumption is made with the amount of data the OP posted.
I would delete the redirect, and recreate it, just for incase. Or inspect the .htaccess if you know much about .htaccess files

 

[RSkeens]

not quite. cPanel (a hosting control panel) has a facility where an end user can quickly setup a redirect, which basically creates a .htaccess file. The problem is that quite often the end user doesn't see the changes immediately since the website is caches on his PC, his ISP's transparent proxy(s), and depending the type of website (i.e. CMS / blog / forum, etc) inside the website's temp / cache folder. If the redirect is to another website, then it could be a DNS cache issue as well.

He then need to clear his cache and force a proxy refresh (can be done by pressing CTRL+F5 multiple times, or adding a "/?" to the URL). He can also test the redirect with an anonymizer proxy, like http://www.proxify.com, http://www.zend2.com/ or http://www.youhide.com/ etc.


This assumption is made with the amount of data the OP posted.
I would delete the redirect, and recreate it, just for incase. Or inspect the .htaccess if you know much about .htaccess files

I am not sure you are familiar with the way cPanel works. Those errors are derived from cPanel and he is getting that when he clicks on the Redirection section from his cPanel account.

This has nothing to do with the actual redirect, because that section isn't even made accessible. Please read the error again, I will highlight the most obvious part: "You might also want to report this error to your web hosting provider.".

 

[SilverNodashi]

I am not sure you are familiar with the way cPanel works. Those errors are derived from cPanel and he is getting that when he clicks on the Redirection section from his cPanel account.

This has nothing to do with the actual redirect, because that section isn't even made accessible. Please read the error again, I will highlight the most obvious part: "You might also want to report this error to your web hosting provider.".

You're right, I have no idea how cPanel works. Only been using it for 9 years or so.


Did you even read my suggestions? I'm suspecting that the host might have changed his cPanel skin (maybe to RVSkins or something), and his PC / ISP's proxy is still caching the OLD COPY of the cPanel pages. Hence why they work on their side, and not his. Try if for yourself, login to one of your client's cPanel (with their account, not as reseller), then changes their skin (to something with a feature removed) and login again, you'll see it's broken. But we also don't know how the host tested it. Did they login as the reseller user, or as this user? We both assume what the problem is, so I would appreciate you keep your insults to yourself, unless you have root access to the server and know 100% what the actual fault is.

 

[RSkeens]

We both assume what the problem is, so I would appreciate you keep your insults to yourself, unless you have root access to the server and know 100% what the actual fault is.

We provide cPanel web hosting and I am pretty sure you were aware of that before lecturing me on what cPanel is. Your previous suggestions are wrong but your RVSkin suggestion may well be right, however the web host will need to do their job and read the error log.

I am sure we can both agree that the web host is likely not telling the truth about the Redirect section working as it is a higher chance that the client's cache is not the cause of it in my opinion.

 

[James]

What is with the hostility RSkeens, all you are doing is coming off looking like a twat

 

[D.B.Cooper]

Whoah! I didn't mean to start an argument here. What is actually happening is that after I enter the relevant details and click the "add" button the error message appears. Nothing is added to the .htaccess file. As far as my hosting provider can tell everything is fine on their side. Or so they say in any event. I can see the redirects I added manually to the .htaccess file under cpanel, I just can't use it to write to the file.

I've added the redirects that I required so this is a bit academic at this point. Everything else seems to be working fine as far as I can tell.

 

[RSkeens]

Whoah! I didn't mean to start an argument here. What is actually happening is that after I enter the relevant details and click the "add" button the error message appears. Nothing is added to the .htaccess file. As far as my hosting provider can tell everything is fine on their side. Or so they say in any event. I can see the redirects I added manually to the .htaccess file under cpanel, I just can't use it to write to the file.

I've added the redirects that I required so this is a bit academic at this point. Everything else seems to be working fine as far as I can tell.

You'll need to ask them to go over the server's error logs and see exactly why that error is thrown. Even if it is working on their side, that error was created and will have been logged.

Luckily you can still add to the .htaccess file manually though, so it's to too bad