Try another browser.
tried many PCs in different cities and didnt open
Agh. Iâm confused by all the random unrelated screenshots in this thread.
If itâs not running you need to look at the log!
You need to look at the end of the log, not the beginning. You need to see why it wonât start now, not events that happened months ago when the log started.
OK. How do we see whatâs past the âFailed to bi>â?
Is this as wide as the screen allowed? <CTLR>-
(control and minus sign) will make the terminal font smaller. Make the terminal as wide as you can and make the font as small as needed until you see the full output.
I donât know how Webmin handles the pid file. I guess first check to see if you have a stale one that is causing problems?
root@main:/var/webmin# ls -lath /var/webmin/ |grep pid -rw-r--r-- 1 root root 8 Dec 25 15:30 lookup-domain-daemon.pid -rw-r--r-- 1 root root 5 Dec 25 15:30 miniserv.pid
Try and look into the logs directly.
less /var/webmin/miniserv.log
Typing a capital G will take you to the end of the log.
please look to the upper message
26th of dec, bit old.
Have you tried just rebooting the server?
yes i reboot it from hostinger and didnt solve. but my website already stopped in this history 26th and i leave it until now . but now i want to solve the problem
yes i reboot it from hostinger and didnt solve. but my website already stopped in this history 26th and i leave it until now . but now i want to solve the problem
Your website has nothing to do with Webmin. They use completely separate web servers, and there is no dependency in either direction.
If you have a problem with your website, it cannot be related to Webmin, and vice versa.
So, letâs focus on one problem at a time. This topic is about Webmin not starting.
We need to see some kind of error in the log. Right now the log does not match what youâre showing us with the status in systemctl
. There is no way Webmin would fail to start without logging something about the failure.
So, you need to tail the log: tail -f /var/webmin/miniserv.error
And, then restart the Webmin service in another terminal: systemctl restart webmin
And, tell us what shows up in the Webmin error log.
Back to:
I think you have a port error. Iâm thinking it is saying âfailed to bindâ and could not listen. But this is just a guess. You can use CTR -
several times and the font should continue to get smaller.
root@main:~# netstat -ap |grep 10000
udp 0 0 0.0.0.0:10000 0.0.0.0:* 1854/perl
Is that your IP? at top of log.
this command didnt give me any output: netstat -ap |grep 10000
and this tell me udp not found: udp 0 0 0.0.0.0:10000 0.0.0.0:* 1854/perl
no this is my ip: 62.72.5.173
âtimeout was exceededâ is a weird error. I canât imagine what it could be waiting on.
Is this system out of memory or disk? Is something consuming a tremendous amount of resources?
Show us:
df -h
And:
top
(Hit q
to exit.)
And:
uptime
And:
free