-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't start daemon : "failed to allocate gateway (172.18.0.1): Address already in use" #419
Comments
Ok I have found a workaround after digging into the daemon code. The IP 172.18.0.1 comes from here : https://github.com/Pterodactyl/Daemon/blob/0a44d9ce34ce469f8481db06a1a6036efc82a4d7/src/controllers/network.js#L70 I have added this to my core.json config and now it works.
|
You already have the pterodactyl ip addresses in use in docker. You can edit the core.json to change the pterodactyl_nw ip address. Similar to this. |
It is such a rare issue that we don't have it prominently linked anywhere, however there is documentation in the sidebar for the Daemon. https://daemon.pterodactyl.io/docs/customizing-network-interfaces |
Ok thank you |
Updated link just in case some other people stumble upon this: |
I have followed the guides to install the panel (v0.5.7) and the daemon (v0.3.7).
The panel works properly. However I don't manage to start the daemon.
I have used the auto installer for the daemon.
I have added the node json config under
/srv/daemon/config/core.json
as shown in the docsBut then when starting the daemon as root with
npm start
I getCan you help me figure this out ?
Thanks
Versions:
System: Linux LC-13234 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19) x86_64 GNU/Linux
PHP: PHP 7.0.18-1~dotdeb+8.1
Docker: Docker version 17.04.0-ce, build 4845c56
NPM: 3.10.10
NodeJS: v6.10.2
Pterodactyl panel: v0.5.7
Pterodactyl dameon: v0.3.7
The text was updated successfully, but these errors were encountered: