Http error 503 - Backend fetch failed

[adler96]

All the php code in my site is developed by me, including the URL you have posted, and it does not generate any icons like those. It's so strange...

I do use some third party Javascript libraries but those run on the client side and cannot generate any files on the server.

 

[spacresx]

judging from the icons folder content it has to do with apache files.
or some apache related script.
is it possible the icons folder is statically created by some code ?

 

[adler96]

judging from the icons folder content it has to do with apache files.
or some apache related script.
is it possible the icons folder is statically created by some code ?

Not from my code; I don't generate icons. The only icons I use are static ones.

I would say there is some server configuration issue exposing some default /icons folder. Maybe the folder is created by the installation script and has more priority than my content?

 

[spacresx]

id guess its like you said, looks more like the overall installation script.
if it relates to apache server, which in itself would seem odd on your website.
since your not running the "apache webserver" in a way to effect your website.

it is concerning to have folders generated that you do not create yourself.
definitely worth getting to the bottom of it to find out whats going on.

As for it being an x10hosting server thing though, that is very unlikely.
i havent seen any other related posts to exposed folders like that.
id say it has more to do with the installation script/scripts than the server.
maybe even a database related thing, but thats just my opinion.

 

[adler96]

This issue started when I was moved from cPanel to DirectAdmin. It was working perfectly before. Maybe during that migration something was not configured correctly?

 

[adler96]

Please note that the issue with the /icons folder is still present. When I access https://www.nightearth.com/icons/ I see a folder that does not belong to my site, and which I cannot see at all when checking my files via FTP.

 

[garrettroyce]

Can you temporarily disable CloudFlare? I'm not very familiar, but I thought you can force it to stop proxying. If you, could you please just set the DNS to use x10 instead of CloudFlare?

This issue seems really confusing and I think CloudFlare just muddies the waters with a layer of protection and indirection that x10 staff can't see through.

If you don't want to do that, please try deleting your CloudFlare DNS and adding it again; perhaps it's an issue on their end? Make sure that any A records point to your server, x12, which is at 198.91.81.12, and any NS records are the x10 nameservers ns1.x10hosting.com and ns2.x10hosting.com. Your mail records go to Amazon, so it does not appear that you need to update your MX records unless you wish to use x10's servers.

 

[adler96]

Hi, thanks for your message. I have tried to disable the proxying in Cloudflare, but the site breaks due to mixed http/https content (I am using Cloudflare to expose the site as https.

I have also deleted the DNS entries, and re-created them again, uing "A" or "CNAME" (I've tried both), but it makes no difference. So the issue is still present.

 

[garrettroyce]

It seems like CloudFlare is serving something that is not your website, but without seeing what it's serving, I'm not sure what to say. There's only one valid server your account is on and it should only output what you tell it to.

Perhaps you could dump your domain registrar settings and your CloudFlare settings? I'm thinking it's a DNS issue, perhaps something pointing to an x10 backup server, but I can't see what's behind CloudFlare.

If it's not a DNS issue, then I don't have any other ideas other than to point the domain somewhere else and see what happens.

 

[adler96]

On my domain registrar I am just pointing to Cloudflare's name servers: leia.ns.cloudflare.com, nick.ns.cloudflare.com, and on Cloudflare I have right now two A entries:

A nightearth.com 198.91.81.12
A www 198.91.81.12

I have disabled the Cloudflare proxying, disabled all https settings in Cloudflare and changed the code of my site to http-only.

So now https doesn't work, but at least Cloudflare is no longer in the middle. Is there anything we can check now?

 

[adler96]

I have additionally just bypassed Cloudflare altogether. My domain registrar is now directly pointing to x10's name servers ns1.x10hosting.com / ns2.x10hosting.com. The issue persists.

 

[garrettroyce]

Can we restore the backup of your account before the CPanel to DirectAdmin transition? Your information looks correct. I can't see your files directly, but if there is a mismatch, between your account and what's on the web, maybe that will help.

 

[adler96]

garrettroyce: Sure, I have no idea of what does it entail, but anything that we can do to try to solve the mystery of these files that are being exposed to the Internet out of thin air, that will be welcome.

 

[garrettroyce]

@Anna can you please restore this account to the backup at the transition to DA? Can you also please check if there is a reason that http://nightearth.com is linked to a different hosting account?

 

[Anna]

I doubt that re-restore would help, but I can check if the package is present if you are willing to give it a go. Interestingly enough, the /icons/ works even if that folder is not in there (renamed it quickly to test), though not too surprising given the issue.

@garretroyce: If it was linked to another account, then the whole site would be wrong and not just the one folder, that's the odd part I'd say.

 

[garrettroyce]

The icons folder is because of mod_autoindex, I think. Apache is creating the folder because Options +Indexes in .htaccess (or should I say, lack of -Indexes)?

https://httpd.apache.org/docs/2.4/mod/mod_autoindex.html

It's not clear from the documentation, but the pictures used in the automatic index are in the /icons/ folder, so Apache is creating this fake directory so the links to the icons work.

What a wild goose chase.

 

[Anna]

The icons folder is because of mod_autoindex, I think. Apache is creating the folder because Options +Indexes in .htaccess (or should I say, lack of -Indexes)?

https://httpd.apache.org/docs/2.4/mod/mod_autoindex.html

It's not clear from the documentation, but the pictures used in the automatic index are in the /icons/ folder, so Apache is creating this fake directory so the links to the icons work.

What a wild goose chase.

Yeah, looks like you are on to something there, I just did a test and I get the exact same listing if I do /icons/ on my url for the free account I have. Somewhat annoying, but appears to be from the server itself.

No idea if it can be blocked in some way, but I'll check that out a bit.

 

[garrettroyce]

Yeah, looks like you are on to something there, I just did a test and I get the exact same listing if I do /icons/ on my url for the free account I have. Somewhat annoying, but appears to be from the server itself.

No idea if it can be blocked in some way, but I'll check that out a bit.

I think you can do it through

Options -Indexes

Or by using RewriteRule. But I think doing the autoindex and also creating your own icons folder is not a good mix. Renaming the folder or turning off autoindexes would be my recommendation.

 

[Anna]

Directory listing is off by default on DA, so that's not it, I added that line to my .htaccess just to be sure and no difference.

 

[garrettroyce]

Maybe this?

IndexOptions +SuppressIcon

Or disable the fancy index

IndexOptions -FancyIndexing

FancyIndexing
This turns on fancy indexing of directories.

SuppressIcon
This will suppress the icon in fancy indexing listings. Combining both SuppressIcon and SuppressRules yields proper HTML 3.2 output, which by the final specification prohibits img and hr elements from the pre block (used to format FancyIndexed listings.)