Recently I was trying to run an completed website on a hosting of my client. On my hosting, wedos.net, everything works properly, so does when running on my localhost. But on this particuluar hosting (Forpsi.com), lot of things act strange.
The thing that I found most annoying, is that server returns 404 Error on a files that exist - but only for *.svg, *.otf, *.woff files etc..
*.php, *.html, *.css,... Each one of these work properly. Not sure where is the issue.
According to this problem, my fonts won't load, neither do my svg files.
Any ideas?
Sounds like your host has a blacklist of extensions, you should ask them if they got any filters in Apache Module mod_access
You can host these elsewhere if you can't resolve it in this server
Related
I have a godaddy website hosted through cPanel, but the html file, named test.html, will not appear when searching "website_name"/test.html. This is the contents of the file:
<!DOCTYPE html><head></head><body>TEST</body></html>
There is no .htaccess, although permissions are set to 644. The server displays the 500 error regardless of whether a valid address was entered. Additionally, the DNS domain and the actual ip address show different things: The DNS shows an index page I can't find in my public_html, whereas the ip shows the godaddy "Future home of something quite cool." message.
Background: I inherited this project as part of a new job. I can set up an apache server with php and mySQL support (in fact I went from using an xampp install to just running everything from command line for practice), but my employer has two godaddy domains: one made using a website building, and one using cPanel for which I am to write my own HTML, CSS, php, js, etc. I have searched extensively across godaddy, google and stack exchange, and have found nothing so far that has worked. The cPanel File Manager has a couple files in it, but nothing will open as a url (I can edit the files though). I checked the godaddy documentation and follow the tutorials and nothing has helped. Any help is appreciated. As an aside, I’m wondering if it would just be easier to completely restart the whole process? The html/css/php files are kind of a hodgepodge and would require rewrites anyway, and bootstrap is used as a source file in every one but never actually implemented. The environment is very relaxed so long as I’m working on something productive.
I have deployed a PHP website do an OpenShift PHP 5.4 Cartridge. The application loads just fine, CSS, JS, etc. but images do not load correctly. The images exist in the git repo which is being pushed to OpenShift just fine but when I attempt to access an image, say from http://someopenshiftapp/images/logo.jpg it fails with a 500 error.
The server log gives me:
/app-root/runtime/repo/images/.htaccess: Invalid command 'IndexIgnore', perhaps misspelled or defined by a module not included in the server configuration
I am trying to resolve this issue but so far google has not been able to help me. I tried editing the httpd.conf to include the module but that is a read only file. I may have to create a new cartridge from scratch? How do I serve images with OpenShift?
I don't know the exact reasons why Apache was behaving like this but it was. There was a robots.txt file disallowing all user agents in the image directory that another developer had added. This was causing the Apache installation to give a 500 error when attempting to access resources within the images sub-directory. If anyone has any further explanation I am willing to listen but for now this mystery is solved.
I may test this exact case in a stand alone Apache environment unrelated to OpenShift and attempt to reproduce this error. :) Happy Coding.
I have a basic web site (just html, js and css files) that I want to host on IIS on my local machine for testing purposes. The site runs fine when I run it directly as a file on my computer. I added a website on IIS, using the directory these files are located in, but when I try to launch it, I get an error page that says:
An error occurred loading a configuration file: Failed to start monitoring changes to '[my site path]' because access is denied.
It then says that the source file is a web.config. I know that ASP.NET sites use a web.config, but I don't even have one, and I just want to run a basic site using html, css, and javascript.
Any ideas on what the fix might be? I made sure I have an application pool for the site.
You likely put it into your user profile -- ie c:\users\skitterm\ -- which won't let the process running IIS read the folder. You are better off using IIS' built in directory structure in c:\inetpub and adding a folder for your site.
As you can tell this is a server misconfiguration. It would help to know the version of your IIS.
You can follow the steps on Microsoft's official knowledgebase to resolve the issue:
http://support.microsoft.com/kb/316721
http://support.microsoft.com/kb/317955 (for IIS v6.0, try Method 3)
I worked in IIS about a year ago and such errors are caused by misconfigured Security settings in IIS.
Sounds like you need to set up the proper access rights for the folder to the account specified by the application pool identity.
First make sure that your folder is not anywhere under your \users\, \program files\, or any other place that already has restricted access. Put it under a folder on the root (\inetpub is a good place).
Then, add the appropriate permissions (usually read only) for the folder to allow the user account specified by the app pool identity to access it. If the app pool identity is set to ApplicationPoolIdentity, adding the IIS_IUSRS local group should do it. Otherwise, use the account that is specified.
This should fix the problem.
I have a very simple MAMP setup, with my index.php and related files in my htdocs folder. I was rolling along fine last night, being able to access the files by typing in things like localhost/index.php. Now, all of the sudden, I get 404s (file not found on this server) when I try to connect to any of the pages that are in my localhost folder or subdirectories of it.
What's more, when I just type in localhost, it shows me some of the directories but DOES NOT show any of my .php files, even though they show up when I perform a ls in the command line.
My MAMP app shows that I am connected to my Apache/MySQL servers. I can still access the localhost/MAMP homepage. But for some obscene reason, all of the sudden my php files are inaccessible. I have changed nothing inside of them! What's going on?
Edit: Turns out I needed to change the permissions of my php files -- they were set to read and write only for sudo and read only for everyone else. I ran chmod 777 on the applicable files and things were back to normal, but this begs several questions:
Why was it working earlier then changed without me ever modifying the file permissions?
Why should I have to make it writeable for other users to be able to access it on my local host as the admin user?
If I were to deploy this code in the wild (I know MAMP isn't used that often in the wild, but still), what would I do? Wouldn't creating these kinds of permissions result in serious security holes?
EDIT 2: Aaaaaand now it's not working again. Again, no changes made to file preferences, etc., just a few tweaks to the actual php files themselves. I don't have any sharing enabled under my sharing settings in System Preferences... this behavior is really starting to become frustrating.
Open Activity Monitor and make sure all instances of Apache and MySQL are closed. Sometimes MAMP has a tendency to not actually quit those processes and the next time you start it up they're still running and it generally messes with things (how's that for a technical explanation?).
Make sure there isn't any other process that's trying to use localhost for any reason. I came across this problem with POW installed. The POW process had stopped responding and it ended up interfering with MAMP's Apache.
Make sure that MAMP's settings haven't somehow been changes. I've seen MAMP revert custom document roots for seemingly no reason which can cause this.
I'd say even before any of this open your system preferences and make sure your Mac's own built-in Apache is off. You'll be able to see this in the Sharing section (it looks like its been moved in Mavericks however).
Make sure you're not routing traffic through a VPN or SSH using Sidestep. I had this problem after going back to an old project I built with MAMP while working from a coffee shop.
I just set up Aptana and have configured the Apache testing server in the folder C:\Apache\htdocs. When I try to test a simple HTML file I am directed to localhost/myproject/myfile.html but I get a 404 error. Upon inspecting the folder I find it empty. If I put a file in that folder the external server displays it just fine, but Aptana is not loading the files on the testing server when I attempt to run them. Any ideas? I know it's something simple, but I can't seem to figure out the problem.
Thanks,
Rob
The solution I discovered for this seems like a workaround but may be the only way to perform the task. I simply set up the localhost server just as if I was publishing the site to a remote location. Of course, the files don't update automatically when viewed like Dreamweaver does, but it works.
I discovered the best solution to this problem. I discovered I needed to install an FTP server on the local machine. I installed and configured Filezilla server and voila - problem solved. The only tip I'd add is to make sure to set the permissions properly for the folder or you'll run into errors.