Hi
for no reason, I can't reach domain.tld:8080 anymore to go into the interface. I didn't change anything.
Is there a apache config file anywhere where I can figure out where it binds to ?
Hi
for no reason, I can't reach domain.tld:8080 anymore to go into the interface. I didn't change anything.
Is there a apache config file anywhere where I can figure out where it binds to ?
check if all services are running, especially nginx. if not, look into the log files. report back when you acquire some more information
There is literally nothing in the apache logs.
I am using a Dynamic-DNS service and my domain does a CNAME to it.
let's say the DDNS is: example.ddns.net
The hostname is ewtwserv
The hostname -f is ewtwserv too...
Tho my hosts file looks like this:
127.0.0.1 ewtwserv localhost
192.168.1.105 ewtwserv.craftnbuild.de ewtwserv
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
The first two lines of a
Also, as in htop there are 5 nginx Processes:
nginx: master process nginx
nginx: worker process
nginx: worker process
nginx: worker process
nginx: worker process
In the apache config for my main domain (craftnbuild.de.conf):
ServerName craftnbuild.de
ServerAlias www.craftnbuild.de vu2005.craftnbuild.de
That seems right to me ...
EDIT:
Result of the 2 command you told me:
root@ewtwserv:~# service imscp_panel restart
root@ewtwserv:~# service nginx restart
Job for nginx.service failed. See 'systemctl status nginx.service' and 'journalctl -xn' for details.
I tried systemctl status nginx.service:
root@ewtwserv:~# systemctl status nginx.service
● nginx.service - A high performance web server and a reverse proxy server
Loaded: loaded (/lib/systemd/system/nginx.service; enabled)
Active: failed (Result: exit-code) since Do 2015-06-11 22:03:10 CEST; 7s ago
Process: 1991 ExecStart=/usr/sbin/nginx -g daemon on; master_process on; (code=exited, status=1/FAILURE)
Process: 1989 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=0/SUCCESS)
Jun 11 22:03:08 ewtwserv nginx[1991]: nginx: [emerg] bind() to 192.168.1.105:8080 failed (98: Address already in use)
Jun 11 22:03:08 ewtwserv nginx[1991]: nginx: [emerg] bind() to [::]:8080 failed (98: Address already in use)
Jun 11 22:03:08 ewtwserv nginx[1991]: nginx: [emerg] bind() to 192.168.1.105:8080 failed (98: Address already in use)
Jun 11 22:03:08 ewtwserv nginx[1991]: nginx: [emerg] bind() to [::]:8080 failed (98: Address already in use)
Jun 11 22:03:09 ewtwserv nginx[1991]: nginx: [emerg] bind() to 192.168.1.105:8080 failed (98: Address already in use)
Jun 11 22:03:09 ewtwserv nginx[1991]: nginx: [emerg] bind() to [::]:8080 failed (98: Address already in use)
Jun 11 22:03:09 ewtwserv nginx[1991]: nginx: [emerg] bind() to 192.168.1.105:8080 failed (98: Address already in use)
Jun 11 22:03:09 ewtwserv nginx[1991]: nginx: [emerg] bind() to [::]:8080 failed (98: Address already in use)
Jun 11 22:03:10 ewtwserv nginx[1991]: nginx: [emerg] bind() to 192.168.1.105:8080 failed (98: Address already in use)
Jun 11 22:03:10 ewtwserv nginx[1991]: nginx: [emerg] bind() to [::]:8080 failed (98: Address already in use)
Jun 11 22:03:10 ewtwserv nginx[1991]: nginx: [emerg] still could not bind()
Jun 11 22:03:10 ewtwserv systemd[1]: nginx.service: control process exited, code=exited status=1
Jun 11 22:03:10 ewtwserv systemd[1]: Failed to start A high performance web server and a reverse proxy server.
Jun 11 22:03:10 ewtwserv systemd[1]: Unit nginx.service entered failed state.
Re;
The panel is not reachable through Apache2. Thus here, you cannot find any relevant information in Apache2 logs...
To resume here: You must check your exotic configuration. This is not an i-MSCP problem. The dynamic DNS are something weird and you must really know what you're doing if you want use them.
Since I was angry enough I just killed the process occupying by using
sudo fuser -k 8080/tcp
Then i started it again. Pling it works again xD Thanks for the help tho
and since the panel is running on nginx, you won't find problems in apache log. i think you could do well, if you read some ebooks about linux at all, and use search in our forum. and understand how i-MSCP is working.
i want to say, its nice that you try things out for learning purposes. but maybe a hosting panel is a little bit too far away to begin with. you need to understand the basic things first.
edit: if you want to host customers, but have no knowhow about server administration, you should start with a reseller (at a managed professional hosting provider) account first. your customers wold issue you in a court, if you mess their sites up