![]() I also recommend to write down any manual changes, so they can be reapplied if necessary. However, I do not know of a detailed documentation of of all these files, so I try to stay on the safe side and possibly not edit the general config files (only those in sites). Use sudo serveradmin stop/start web to do so. Important: If you change the files manually, you must re-start the Apache server in order to make the changes effective. It is not recommended to manually adjust the config files, except for those in the sites subdirectory, because they may get overwritten by the Server app or when updating the Server app. In addition to these, there are two more configuration file in /Library/Server/Web/Config/proxy which configure the proxy services. There is also a file like 0000_127.0.0.1_34543_.conf (no domain name in the file name) which defines the default site. They are named something like 0000_127.0.0.1_34543_ where 34543 is the configuration for the https (SSL) port, while 35480 would indicate the http port. Path /Library/Server/Web/Config/apache2/sites contains config files specific to your websites. the other files contain configurations for specific applications or webapps (the latter being defined in plist files in /Library/Server/Web/Config/apache2/webapps).httpd_server_app.conf - more general configuration.Path /Library/Server/Web/Config/apache2 contains the general config files However, the Server app uses a lot of of different config files which might be relevant: The former might be due to configuring a user group being allowed to access the site, while the latter just means Not found.Īs to your actual question about the config files: ![]() For example, you say you get Forbidden when accessing your site, but later you mention a status 404. You are mixing several aspects in your question which makes it complicated to give a helpful answer. If I change one of them will it be reflected in the other? Do I need to change both of them? Additionally, I don't have DNS set up and am unsure if that was the original issue of not pulling up the new website over the default site. config.orig (original file? and is no longer active)Īlso, OS X Server and Apache seem to have the same files in two different places and I'm a little confused on which one to change. config.prev (I'm assuming this is a previous version or copy of an active config file and is no longer active) config (I'm assuming this is the active file) I don't know what they all mean or if they are active. There seem to be about 4 file extension types. So from there I was going to check into the config files, but there are several, and I just want to know the gist behind them. I've run a syntax checker for Apache in terminal and terminal says syntax is ok. I have read a lot of possibilities as to why this may be happening. So, in an attempt to begin de-conflicting I replaced the files where the default site was located with the new website files and all of the sudden am getting the above 404 message. It was my understanding that Apache would redirect from the default site to the created site automatically once created. OS X Server automatically creates two default websites (one on port 80 and one on port 443). I'm using macOS X Server 5.2 with Apache 2.4.18. You don't have permission to access /index.html on this server.Īpache Server at ffghost.local Port 34580 MBPr:/Users/analysisman/Downloads% python -m SimpleHTTPServer ![]() This is the fastest way to run a Web Server without additional configurations. Just change the directory you want to use and run the following command. Start a Simple Web Server from Any Directory with a Terminal command You need only one CLI command to start a Web Server on macOS.
0 Comments
Leave a Reply. |