#NGIX Support

1 messages · Page 1 of 1 (latest)

distant plank
#

root@r720:/var/www/pterodactyl# nginx -t
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful

--
root@r720:/var/www/pterodactyl# systemctl status nginx.service
● nginx.service - A high performance web server and a reverse proxy server
Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2024-08-08 07:12:49 UTC; 2min 7s ago
Docs: man:nginx(8)
Process: 5906 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=0/SUCCESS)
Process: 5917 ExecStart=/usr/sbin/nginx -g daemon on; master_process on; (code=exited, status=1/FAILURE)

Aug 08 07:12:48 r720 nginx[5917]: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
Aug 08 07:12:48 r720 nginx[5917]: nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)
Aug 08 07:12:48 r720 nginx[5917]: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
Aug 08 07:12:48 r720 nginx[5917]: nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)
Aug 08 07:12:49 r720 nginx[5917]: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
Aug 08 07:12:49 r720 nginx[5917]: nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)
Aug 08 07:12:49 r720 nginx[5917]: nginx: [emerg] still could not bind()
Aug 08 07:12:49 r720 systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
Aug 08 07:12:49 r720 systemd[1]: nginx.service: Failed with result 'exit-code'.
Aug 08 07:12:49 r720 systemd[1]: Failed to start A high performance web server and a reverse proxy server.
root@r720:/var/www/pterodactyl#

half boughBOT
#

@distant plank; Type sudo nginx -t | nc pteropaste.com 99 or sudo systemctl status nginx to find out more more information.

distant plank
half boughBOT
#

@distant plank; Type sudo nginx -t | nc pteropaste.com 99 or sudo systemctl status nginx to find out more more information.

distant plank
tall yarrow
distant plank
#

You do not need to symlink this file if you are using CentOS.

sudo ln -s /etc/nginx/sites-available/pterodactyl.conf /etc/nginx/sites-enabled/pterodactyl.conf

You need to restart nginx regardless of OS.

sudo systemctl restart nginx

half boughBOT
distant plank
#

@tall yarrow this is what I've gotten.

half boughBOT
distant plank
#

Plus, the panel will not post on the webserver without nginx.

tall yarrow
#

If you have multiple configurations in your sites-enabled, make sure they don’t conflict with one another.

distant plank
#

There is only one, I do not see extra configs

old spade
#

nginx is already running. What are you trying to do ?

distant plank
old spade
#

nginx is the web server

distant plank
# old spade nginx *is* the web server

I can not access it on my web browser, using domain or ip. That is the issue, when I setup pterodactyl last time before my ds bricked I didn't run into the error code.

old spade
#

Well looks like you've started nginx manually, ouside of systemctl

#

So start by killing it killall nginx

#

Then try to restart nginx with systemctl

distant plank
#

I don't have that error anymore, thank you. Though. I still am not able to access the webserver on the browser. Do you happen to know what would cause that?

old spade
#

Most likely firewall or other network mis-configuration

distant plank
#

This is what I get, do you have any specific ideas?

image.png
old spade
distant plank
#

The interesting thing, all ports for pterodactyl are open

tall yarrow
#

On a side note, does your path to that configuration file actually contain a second //etc/ directory at the end?

distant plank
tall yarrow
#

Well, you can start with the nginx error logs if you haven’t already

distant plank