Skip to main content
Participant
February 26, 2017
Answered

404 on Linux servers

  • February 26, 2017
  • 2 replies
  • 563 views

I have just moved a website across from one Linux remote server to another. The website worked perfectly on the 1st server but now on the 2nd server  the website won't display some icons triggered from a CSS file. On investigation the CSS file is in place on the server in the correct relative place but in the logs I am seeing a 404 for the icon responsible CSS file. The website is an exact mirror of the one on the first server with the same site relative paths and root. It's quite a complex website and all the other features are working fine on the 2nd server - just missing icons.

In the grand scheme of things a few missing icons is not going to end the world but it is bugging me..  Any ideas  ?   Could try absolute path for the one CSS file  ?

This topic has been closed for replies.
Correct answer Jon Fritz

I asume you meant to type: xmediatest2.biz.

The file is def on the server with the same links and file case structure..

The hosting company is telling us it's a website issue....

Uhmm..


Sorry, missed the second "t" in the address, just a type-o in the reply.

In my experience, either the file is at the location, or it's not. There's nothing to set in DW to "upload to server but do not serve it to browsers when requested"

When I browse to your icons folder at www.xmediatest2.biz/icons, there is no flaticon.css file listed in the directory at all...

However, there is a note I've never seen before about "public domain icons" showing under the file list.

As a test, make a new folder called css_icons, place your flaticon.css file within that, link to it and upload all the related files.

I bet it works.

I'm thinking your server is only allowing "icon file types" in that icons folder and .css wouldn't fit the bill on allowed file extensions by the server (or some silliness).

EDIT: The reason I suggest making the new folder is because I'm willing to bet the "icons" folder on your current server, given the server-generated notation about public use icons, has been set to only allow certain file types. If that's the case, shortly after you upload the .css (a non image/icon related file type) the server could be auto-deleting it.

2 replies

Jon Fritz
Community Expert
Community Expert
February 27, 2017

Could you post a link to one of the pages in question?

Fresh eyes may spot the error for you.

Participant
February 27, 2017

Thanks. A bottle of scotch for whoever wrks this one out..

The website is located on URL: xmediatest2.biz.

The icons should be located within the six red spheres in the 'why us' section on the home page. 

(don't worry the html for the other pages aren't uploaded yet..).

The server log is showing a 404 for a file called  icons/flaticon.css which is present on the server in the correct relative place.

To recreate the situation - viewing the website from local files the website wrks perfectly. When I remove that css file the icons vanish just as on the remote live server.

An identical website wrks perfectly on another Linux remote server.

Jon Fritz
Community Expert
Community Expert
February 27, 2017

The server is telling our browsers there is no file called flaticon.css at www.xmediates2.biz/icons/

...if the "icons" folder or the "flaticon.css" file have any difference in case structure from the link being used, that would be expected. If there's absolutely no difference AND the file has, for sure, been uploaded to...

"your site root" > icons > flaticon.css

...you'll definitely need to talk to the hosting company. For some reason the server isn't recognizing the file and sending it to the browser when requested.

Rob Hecker2
Legend
February 26, 2017

Could it be a Linux permissions/ownership issue?

Less likely would be HTTP access permissions in Apache

Directory name case issue (example: icons and Icons are not the same).

Participant
February 26, 2017

Thanks but none of those. It wouldn't be a case sensitive issue as a replica website worked perfectly on a different Linux remote server before.