Page 1 of 1

can't connect to LocalHost

PostPosted: 21. March 2023 21:38
by FoxintheHole
I have worked for a week trying to figure this out:
MY htdocs file:
I have xampp and I think it may by in by index.php file under htdocs. This is what is looks like:



<?php
if (!empty($_SERVER['HTTPS']) && ('on' == $_SERVER['HTTPS'])) {
$uri = 'https://';
} else {
$uri = 'http://'; }
$uri .= $_SERVER['HTTP_HOST'];
header('Location: '.$uri.'/dashboard/');
exit;
?>
Something is wrong with the XAMPP installation :-(

[color=#00BF00][color=#00BF00]I have unstalled xamapp and reinstalled multiple times and this file gives me the same message
. [/color]
Here is my start.bat file[/color]

Diese Eingabeforderung nicht waehrend des Running beenden
Bitte erst bei einem gewollten Shutdown schliessen
Please close this command only for Shutdown
Apache 2 is starting ...
(OS 10048)Only one usage of each socket address (protocol/network address/port) is normally permitted. : AH00072: make_sock: could not bind to address [::]:9090
(OS 10048)Only one usage of each socket address (protocol/network address/port) is normally permitted. : AH00072: make_sock: could not bind to address 0.0.0.0:9090
AH00451: no listening sockets available, shutting down
AH00015: Unable to open logs

Re: can't connect to LocalHost

PostPosted: 21. March 2023 23:28
by Nobbie
FoxintheHole wrote:(OS 10048)Only one usage of each socket address (protocol/network address/port) is normally permitted. : AH00072: make_sock: could not bind to address [::]:9090
(OS 10048)Only one usage of each socket address (protocol/network address/port) is normally permitted. : AH00072: make_sock: could not bind to address 0.0.0.0:9090


Xampp does not configure Port 9090 at all. Did you forget to tell us about that?

Re: can't connect to LocalHost

PostPosted: 22. March 2023 06:50
by Altrea
FoxintheHole wrote:I have unstalled xamapp and reinstalled multiple times and this file gives me the same message

What you showed us is not the actual message you get as output. It's just the plain text.
This message on the bottom of the file will only occure on the screen if the file is requested by a browser correctly and the redirect failes.

Your actual problem is that you are trying to start Apache on port 9090 and this port is already in use.
Nobody knows why your Apache is listening on port 9090 (default would be 80 and 443) and why there is already another process listening on that port.

Changing the Apache ports does have some sideeffects. You can read more about this here: [Q&A] Changing the Apache default ports