Certbot Renew did not work

rg305 · October 27, 2019, 6:32pm

So restart docker?

Deathmerc · October 27, 2019, 6:39pm

I restarted it, however it’s is already constantly running
so it gave me this

18:34:07.573Z  INFO wings: + ------------------------------------ +
18:34:07.576Z  INFO wings: | Running Pterodactyl Daemon v0.6.12    |
18:34:07.576Z  INFO wings: |        https://pterodactyl.io        |
18:34:07.576Z  INFO wings: |  Copyright 2015 - 2019 Dane Everitt  |
18:34:07.576Z  INFO wings: + ------------------------------------ +
18:34:07.576Z  INFO wings: Loading modules, this could take a few seconds.
18:34:08.231Z  INFO wings: Modules loaded, starting Pterodactyl Daemon...
18:34:08.367Z  INFO wings: Configuring user pterodactyl (id: 999) as the owner of all server files.
18:34:08.374Z  INFO wings: Configuring timezone file location...
18:34:08.374Z  INFO wings: Checking container networking environment...
18:34:08.393Z  INFO wings: Found network interface for daemon: pterodactyl_nw
18:34:08.393Z  INFO wings: Ensuring correct network interface for containers...
18:34:08.413Z  INFO wings: Networking gateway detected as 172.18.0.1 for interface: pterodactyl0.
18:34:08.421Z  INFO wings: Contacting panel to retrieve a list of currrent Eggs available to the node.
18:34:08.583Z  INFO wings: Checking existing eggs against Panel response...
18:34:08.588Z  INFO wings: Beginning server initialization process.
18:34:08.641Z  INFO wings: Server status has been changed to ON (server=2ad44147-dbbb-457f-8172-ef9fb6a42b93)
18:34:08.648Z  INFO wings: Server status has been changed to ON (server=319c87b8-ea4b-4b40-bb9c-dc4b576af6b7)
18:34:08.650Z  INFO wings: Server status has been changed to ON (server=40735cb2-ba95-4f0e-b482-64ba03f80678)
18:34:08.665Z  INFO wings: Server status has been changed to ON (server=6a8446f1-0c26-41fc-b030-244e39896059)
18:34:08.668Z  INFO wings: Server status has been changed to ON (server=8510c0c3-017f-44d5-9258-6341a09b4783)
18:34:08.671Z  INFO wings: Server status has been changed to ON (server=a52dc352-0ff6-4667-bf6d-f46bc63856fb)
18:34:08.675Z  INFO wings: Server status has been changed to ON (server=e2f3801f-c334-427e-b68b-0a9c449476af)
18:34:08.696Z  INFO wings: Daemon detected that the server container is currently running, re-attaching to it now! (server=2ad44147-dbbb-457f-8172-ef9fb6a42b93)
18:34:08.706Z  INFO wings: Daemon detected that the server container is currently running, re-attaching to it now! (server=319c87b8-ea4b-4b40-bb9c-dc4b576af6b7)
18:34:08.715Z  INFO wings: Daemon detected that the server container is currently running, re-attaching to it now! (server=40735cb2-ba95-4f0e-b482-64ba03f80678)
18:34:08.726Z  INFO wings: Daemon detected that the server container is currently running, re-attaching to it now! (server=6a8446f1-0c26-41fc-b030-244e39896059)
18:34:08.735Z  INFO wings: Daemon detected that the server container is currently running, re-attaching to it now! (server=8510c0c3-017f-44d5-9258-6341a09b4783)
18:34:08.750Z  INFO wings: Daemon detected that the server container is currently running, re-attaching to it now! (server=a52dc352-0ff6-4667-bf6d-f46bc63856fb)
18:34:08.760Z  INFO wings: Daemon detected that the server container is currently running, re-attaching to it now! (server=e2f3801f-c334-427e-b68b-0a9c449476af)
18:34:08.963Z  INFO wings: Configuring websocket for daemon stats...
18:34:08.963Z  INFO wings: Configuring internal SFTP server...
18:34:08.981Z FATAL wings: A fatal error occured during an operation. (err.code=EADDRINUSE)
    Error: listen EADDRINUSE 0.0.0.0:2022
        at Server.setupListenHandle [as _listen2] (net.js:1360:14)
        at listenInCluster (net.js:1401:12)
        at doListen (net.js:1510:7)
        at _combinedTickCallback (internal/process/next_tick.js:142:11)
        at process._tickDomainCallback (internal/process/next_tick.js:219:9)

Deathmerc · October 27, 2019, 6:44pm

Also thanks so much for helping me on this

rg305 · October 27, 2019, 6:55pm

Port 2022 ?
Some sort of internal SFTP
Perhaps the load command for it was duplicated somewhere some how.

Deathmerc · October 27, 2019, 6:57pm

uh yeh? ._.

That’s for the sftp it looks like, in the config I posted above

Deathmerc · October 27, 2019, 7:00pm

For the setup, the wings need to be running 24/7 for the node to be connected to the daemon, or something along those lines:

https://pterodactyl.io/daemon/installing.html#starting-the-daemon

forever start src/index.js

# To stop the daemon use:
forever stop src/index.js

rg305 · October 27, 2019, 7:05pm

OK so stop it and check that nothing is using 2022
netstat -pant | grep 2022

If none, then restart it.
If something is still using it, show that line here.
maybe something like this:
tcp 0 0 0.0.0.0:2022 0.0.0.0:* LISTEN 1229/sshd

rg305 · October 27, 2019, 7:11pm

That’s in use by some external IPs.
Looks like probes or actual exploit attempts - LOL
You should protect the port with firewall rules (maybe) or an IPS (at least).
I mean I don’t know it that looks “normal and expected” to you.
[if it doesn’t, then maybe take some action]

Deathmerc · October 27, 2019, 7:13pm

Most is my ip, idk who
223.111.150.40
178.142.11.117
is, but could be my “dev” team for the minecraft servers
Connected to the SFTP of the server. I closed mine just now (Was using filezilla) but still shows my ips up there.

rg305 · October 27, 2019, 7:15pm

path /srv/deamon-data may be at risk (or worse if SFTP program can be exploited further.

Deathmerc · October 27, 2019, 7:17pm

ok… wellllll

I will have to fix that later, but is that the issue atm where I can’t connect to the server’s or…

rg305 · October 27, 2019, 7:21pm

One issue is that it tries to start SFTP on 2022
But that is ALREADY running.
[there may be other issues]

As for IP 223.111.150.40, I would block that “C” class:

[seeing a lot of scans/probes/etc. from it. - nothing good]

Deathmerc · October 27, 2019, 7:24pm

I’m not sure how to do that, if you could assist with that I’d appreciate it

Block the C class

rg305 · October 27, 2019, 7:26pm

You have to be a bit more specific.

On the "port 2022 already in use":
looks like node.js is already using that port.
Can you restart node.js?
Can you reboot the entire system?

Deathmerc · October 27, 2019, 7:29pm

I can, not sure how, and not sure if I want to, because it could cause more issues ? I’m not familiar with rebooting everything

How would I restart the node.js

rg305 · October 27, 2019, 7:33pm

The best what to “block”, is with a firewall.
Not sure what your network looks like, so hard to give any direction [and this is not the forum for that anyway].
One simple way to “block” is to add “blackhole” routes on the system itself (block it with networking routes).
A less tedious method is to use an IPS that actively manages those kinds of things automatically for you.
Adding routes to systems, or rules to firewalls, is very time consuming and usually too “permanent” (not recommended as a first resort for direct end-user action).
In other words, pass that along to whomever protects your network.

rg305 · October 27, 2019, 7:34pm

If you have never done that, then this is not the time to start.
Who manages it?

Deathmerc · October 27, 2019, 7:35pm

Me, I purchased a dedicated server from a hosting site, but everything that is done on it, I have myself through tutorials and such ._.

root@client-03-rs:~# netstat -tulpn | grep 2022
tcp 0 0 0.0.0.0:2022 0.0.0.0:* LISTEN 12422/node
root@client-03-rs:~#

I ran the above command and that popped up ^

The bot in the discord support for pterodactyl told me to enter that.

Deathmerc · October 27, 2019, 7:40pm

Holy crap it got fixed.

I ended up needing to kill the 12422
and then ran
systemctl enable --now wings
and it’s fixed.

I think something else before was changed with it. Do you think I will have to do that every time I restart certbot

Deathmerc · October 27, 2019, 7:49pm

Thank you so much for all your efforts