I installed the Nginx Proxy Manager on the same server and this address already in use error occurred when I started the ASF. How can I fix it
#2947
-
|
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 7 replies
-
|
You've started at least two processes, very likely more, and very likely one of them is holding and actually listening on that port - see your logs. ASF does not support being started more than once from existing directory, and if you intend to start two or more instances (each one in its own directory) then each one must have its own exclusive port, you can't start two on the same one. If you still don't know what holds the port for you, |
Beta Was this translation helpful? Give feedback.
-
|
I used the nginx proxy manager to configure nginx and SSL. (The Internet says it's easy!) |
Beta Was this translation helpful? Give feedback.
-
|
I'll learn how to install nginx right away... Thank you! |
Beta Was this translation helpful? Give feedback.
-
|
If you're not using that docker container for anything else, my recommendation is to drop it, install ASF normally as per setting up guide, and then just use it. You can expose its 1242 port outside of host machine (as stated in IPC section) and you don't need nginx, nginx proxy manager or docker for that, ASF can do it on its own. ONLY after you get it working through However, you shouldn't do all at once since you'll be stuck like now without an idea what to do. Start from simple step - delete nginx, nging proxy manager, docker, and everything unrelated, get ASF running, enable all hosts with custom IPC.config as stated in IPC wiki section, and get this working, because without this step nothing else makes sense. Only once you do, enhance this further to your target scenario. It's not hard, everything related to ASF that you'll need for this you can find in setting up (actually running ASF), IPC (exposing it further) and management (making it start automatically and act as a service) wiki sections. The end setup will be ASF listening on 127.0.0.1:1242, nginx listening on ::80 and ::443, and when you connect to https://asf.yourdomain.com then nginx will on your behalf connect with ASF on 127.0.0.1:1242. Of course you also can technically make your life super complicated using docker, and for that we have a docker section which explains everything ASF-related in regards to docker, but like I said, we don't teach people how to use third-party tools here, so if you want to go that route you'll be expected to dig and resolve issues on your own, and unless you know what you're doing, you should instead get normal setup to run, and only if you get to understand the internals a bit better, you can decide to experiment with docker if you still have time, willings and some reason to - but I don't recommend running ASF inside docker anyway. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you so much for your advice and your help!! I reinstalled the server and asf and added nginx I changed the nginx config. What else do I need to do? |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
You've started at least two processes, very likely more, and very likely one of them is holding and actually listening on that port - see your logs. ASF does not support being started more than once from existing directory, and if you intend to start two or more instances (each one in its own directory) then each one must have its own exclusive port, you can't start two on the same one.
If you still don't know what holds the port for you,
netstat -tulpn | grep 1242will give you the PID.