F5F Stay Refreshed Software Operating Systems The localhost is not responding.

The localhost is not responding.

The localhost is not responding.

Pages (2): 1 2 Next
T
tetriad
Member
203
07-22-2023, 10:37 AM
#1
When launching Apache on MacOS and accessing localhost, it shows a permission error. It seems the issue might be with your setup or permissions. The problem didn’t occur before, so check your configuration or try restarting the service.
T
tetriad
07-22-2023, 10:37 AM #1

When launching Apache on MacOS and accessing localhost, it shows a permission error. It seems the issue might be with your setup or permissions. The problem didn’t occur before, so check your configuration or try restarting the service.

D
duang_luo
Member
72
07-28-2023, 05:08 PM
#2
Need more details about your setup. What type of service or website are you aiming to run behind Apache? Are you sure Apache is active on port 80? If yes, review its logs (access and error) for any access issues. A message like "You don't have permissions" might indicate a missing file or insufficient read rights.
D
duang_luo
07-28-2023, 05:08 PM #2

Need more details about your setup. What type of service or website are you aiming to run behind Apache? Are you sure Apache is active on port 80? If yes, review its logs (access and error) for any access issues. A message like "You don't have permissions" might indicate a missing file or insufficient read rights.

C
Carsland123
Senior Member
398
07-29-2023, 01:35 AM
#3
Refers to the internal localhost page indicating functionality. When Apache is active on Mac, no web pages appear except for the server itself. Confirmed it's running on port 80, not the www version, and it operated before the recent change.
C
Carsland123
07-29-2023, 01:35 AM #3

Refers to the internal localhost page indicating functionality. When Apache is active on Mac, no web pages appear except for the server itself. Confirmed it's running on port 80, not the www version, and it operated before the recent change.

W
WithoutNameHD
Junior Member
25
07-29-2023, 03:20 AM
#4
The "It works" page is merely an HTML file hosted in a specific location on your system. The previous advice remains valid. Review Apache's settings, confirm the directory it's attempting to deliver exists, ensure you have read access to it, and examine its logs for additional details.
W
WithoutNameHD
07-29-2023, 03:20 AM #4

The "It works" page is merely an HTML file hosted in a specific location on your system. The previous advice remains valid. Review Apache's settings, confirm the directory it's attempting to deliver exists, ensure you have read access to it, and examine its logs for additional details.

S
SiberianHusky
Junior Member
14
07-30-2023, 09:01 AM
#5
You're unsure about their location and want to confirm whether the user change was handled correctly.
S
SiberianHusky
07-30-2023, 09:01 AM #5

You're unsure about their location and want to confirm whether the user change was handled correctly.

X
XxAlenxX
Member
118
07-30-2023, 01:51 PM
#6
What macOS version are you running? In Monterey, the configuration file is located at /etc/apache2/httpd.conf. Access it with a text editor to see the serving directory and log output path.
X
XxAlenxX
07-30-2023, 01:51 PM #6

What macOS version are you running? In Monterey, the configuration file is located at /etc/apache2/httpd.conf. Access it with a text editor to see the serving directory and log output path.

J
Juan2610
Posting Freak
875
07-30-2023, 10:10 PM
#7
Sure, just to clarify, you modified only the document root to point to a directory you can easily reach, and it seems to be functioning now.
J
Juan2610
07-30-2023, 10:10 PM #7

Sure, just to clarify, you modified only the document root to point to a directory you can easily reach, and it seems to be functioning now.

S
SQGame
Junior Member
3
08-01-2023, 10:35 PM
#8
I discovered this error message during a test on February 20th at 16:16. The issue stemmed from the directory structure not matching expectations, specifically the missing index.html file. It seems the server-generated index was blocked by an Options directive. I wondered if caching played a role since the page would load even after stopping Apache, but it failed once Apache was down.
S
SQGame
08-01-2023, 10:35 PM #8

I discovered this error message during a test on February 20th at 16:16. The issue stemmed from the directory structure not matching expectations, specifically the missing index.html file. It seems the server-generated index was blocked by an Options directive. I wondered if caching played a role since the page would load even after stopping Apache, but it failed once Apache was down.

G
Grifo24O
Member
181
08-02-2023, 07:06 AM
#9
G
Grifo24O
08-02-2023, 07:06 AM #9

J
JayJayw
Member
54
08-03-2023, 04:02 AM
#10
It appears the issue was resolved by using the correct index.html file. Initially, the expected file wasn't present in the specified folder, but after checking the default location, everything functioned properly. An Apple Support representative confirmed the default settings, and now the document displays correctly. Thank you for sharing the details and for your patience!
J
JayJayw
08-03-2023, 04:02 AM #10

It appears the issue was resolved by using the correct index.html file. Initially, the expected file wasn't present in the specified folder, but after checking the default location, everything functioned properly. An Apple Support representative confirmed the default settings, and now the document displays correctly. Thank you for sharing the details and for your patience!

Pages (2): 1 2 Next