Open devhayslett opened 4 months ago
Seems that the panel is working. Not sure about the issue.
Please run these commands on the server and post the results:
curl localhost:1000
docker ps
Seems that the panel is working. Not sure about the issue.
Please run these commands on the server and post the results:
curl localhost:1000 docker ps
root@ubuntu:~# curl localhost:1000
curl: (7) Failed to connect to localhost port 1000 after 0 ms: Connection refused
root@ubuntu:~# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
8ad4789b360c libertea/haproxy "/entrypoint.sh" 5 minutes ago Up 5 minutes libertea-haproxy
30aadae23e02 libertea/provider-shadowsocks-v2ray "/entrypoint.sh" 5 minutes ago Up 5 minutes 1080/tcp, 127.0.0.1:2003->2003/tcp libertea-provider-shadowsocks-v2ray
3b34e9696ebb mongo:latest "docker-entrypoint.s…" 5 minutes ago Up 5 minutes libertea-mongodb
caa2bdb00c13 nginx:latest "/docker-entrypoint.…" 5 minutes ago Up 5 minutes 127.0.0.1:25898->80/tcp libertea-camouflage-nginx-fallback
a4cd5727269b libertea/provider-vmess-grpc "/entrypoint.sh" 5 minutes ago Up 5 minutes 127.0.0.1:2007->2007/tcp libertea-provider-vmess-grpc
ee6112e6c44d libertea/syslog "rsyslogd -n" 5 minutes ago Up 5 minutes 127.0.0.1:514->514/udp libertea-rsyslog
d8f172a52547 libertea/provider-trojan-grpc "/entrypoint.sh" 5 minutes ago Up 5 minutes 127.0.0.1:2004->2004/tcp libertea-provider-trojan-grpc
68a141da0b0b libertea/log-parser "bash run.sh" 5 minutes ago Up 5 minutes libertea-log-parser
694a40bc854e libertea/provider-vless-grpc "/entrypoint.sh" 5 minutes ago Up 5 minutes 127.0.0.1:2005->2005/tcp libertea-provider-vless-grpc
3aeb3143ca9b libertea/provider-vless-ws "/entrypoint.sh" 5 minutes ago Up 5 minutes 127.0.0.1:2002->2002/tcp, 127.0.0.1:12002->12002/tcp libertea-provider-vless-ws
76b6fac45492 libertea/provider-trojan-ws "/entrypoint.sh" 5 minutes ago Up 5 minutes 127.0.0.1:2001->2001/tcp, 127.0.0.1:12001->12001/tcp libertea-provider-trojan-ws
Here's the output of the requested log. It appears that there is some issue with the cert generation. Could it be a port forwarding issue? If so, what port would I need to forward on my router in order for the cert request to succeed?
uWSGI is running in multiple interpreter mode spawned uWSGI master process (pid: 1431) spawned uWSGI worker 1 (pid: 1490, cores: 1) spawned uWSGI worker 2 (pid: 1491, cores: 1) spawned uWSGI worker 3 (pid: 1492, cores: 1) spawned uWSGI worker 4 (pid: 1493, cores: 1) spawned uWSGI worker 5 (pid: 1494, cores: 1) spawned uWSGI worker 6 (pid: 1495, cores: 1) spawned uWSGI http 1 (pid: 1496) Saving debug log to /var/log/letsencrypt/letsencrypt.log Account registered. Requesting a certificate for xxx.xxxxx.xxx
Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems: Domain: xxx.xxxxx.xxx Type: unauthorized Detail: 2606:4700:3037::ac43:a809: Invalid response from http://xxx.xxxxx.xxx/.well-known/acme-challenge/fxJ1yTRt7grpao3pxuI0EPZPm3HiNcp2twNHDQLuCYI: 521
Hint: The Certificate Authority failed to download the challenge files from the temporary standalone webserver started by Certbot on port 9999. Ensure that the listed domains point to this machine and that it can accept inbound connections from the internet.
libertea-haproxy libertea-haproxy libertea-haproxy libertea-haproxy libertea-haproxy Some challenges have failed. Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details. Sat May 11 04:00:00 2024 - [uwsgi-cron] routing signal 3 2024-05-11 04:00:00 - CRON save_connected_ips_300957 - Saving connected IPs -- creating mongo client on pid 1491 Sat May 11 04:00:00 2024 - [uwsgi-cron] routing signal 4 2024-05-11 04:00:00 - CRON update_certificates_548679 - Updating certificates -- creating mongo client on pid 1490 2024-05-11 04:00:00 - CRON save_connected_ips_300957 - DONE saving connected IPs 2024-05-11 04:01:09 - CRON periodic_update_domains_778805 - Updating domains cache -- creating mongo client on pid 1490 2024-05-11 04:01:09 - CRON update_certificates_548679 - Updating certificate for xxx.xxxxx.xxx *** Generating certificate for xxx.xxxxx.xxx Saving debug log to /var/log/letsencrypt/letsencrypt.log 2024-05-11 04:01:09 - CRON periodic_update_domains_778805 - DONE updating domains cache Requesting a certificate for xxx.xxxxx.xxx
Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems: Domain: xxx.xxxxx.xxx Type: unauthorized Detail: 2606:4700:3037::ac43:a809: Invalid response from http://xxx.xxxxx.xxx/.well-known/acme-challenge/fvj06OWzjOUH1FUdAQhaaQOIOjPs5TkhD5m2pbykBO4: 521
Hint: The Certificate Authority failed to download the challenge files from the temporary standalone webserver started by Certbot on port 9999. Ensure that the listed domains point to this machine and that it can accept inbound connections from the internet.
Some challenges have failed. Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details. 2024-05-11 04:03:09 - CRON periodic_update_domains_348256 - Updating domains cache 2024-05-11 04:03:09 - CRON periodic_update_domains_348256 - DONE updating domains cache 2024-05-11 04:04:09 - CRON periodic_update_users_stats_786405 - Updating users stats cache -- creating mongo client on pid 1492 [Errno 2] No such file or directory: '/root/libertea/./data/usages/day/2024-04-11.json' [Errno 2] No such file or directory: '/root/libertea/./data/usages/day/2024-04-12.json' [Errno 2] No such file or directory: '/root/libertea/./data/usages/day/2024-04-13.json' [Errno 2] No such file or directory: '/root/libertea/./data/usages/day/2024-04-14.json' [Errno 2] No such file or directory: '/root/libertea/./data/usages/day/2024-04-15.json' [Errno 2] No such file or directory: '/root/libertea/./data/usages/day/2024-04-16.json' [Errno 2] No such file or directory: '/root/libertea/./data/usages/day/2024-04-17.json' [Errno 2] No such file or directory: '/root/libertea/./data/usages/day/2024-04-18.json' [Errno 2] No such file or directory: '/root/libertea/./data/usages/day/2024-04-19.json' [Errno 2] No such file or directory: '/root/libertea/./data/usages/day/2024-04-20.json' [Errno 2] No such file or directory: '/root/libertea/./data/usages/day/2024-04-21.json' [Errno 2] No such file or directory: '/root/libertea/./data/usages/day/2024-04-22.json' [Errno 2] No such file or directory: '/root/libertea/./data/usages/day/2024-04-23.json' [Errno 2] No such file or directory: '/root/libertea/./data/usages/day/2024-04-24.json' [Errno 2] No such file or directory: '/root/libertea/./data/usages/day/2024-04-25.json' [Errno 2] No such file or directory: '/root/libertea/./data/usages/day/2024-04-26.json' [Errno 2] No such file or directory: '/root/libertea/./data/usages/day/2024-04-27.json' [Errno 2] No such file or directory: '/root/libertea/./data/usages/day/2024-04-28.json' [Errno 2] No such file or directory: '/root/libertea/./data/usages/day/2024-04-29.json' [Errno 2] No such file or directory: '/root/libertea/./data/usages/day/2024-04-30.json' [Errno 2] No such file or directory: '/root/libertea/./data/usages/day/2024-05-01.json' [Errno 2] No such file or directory: '/root/libertea/./data/usages/day/2024-05-02.json' [Errno 2] No such file or directory: '/root/libertea/./data/usages/day/2024-05-03.json' [Errno 2] No such file or directory: '/root/libertea/./data/usages/day/2024-05-04.json' [Errno 2] No such file or directory: '/root/libertea/./data/usages/day/2024-05-05.json' [Errno 2] No such file or directory: '/root/libertea/./data/usages/day/2024-05-06.json' [Errno 2] No such file or directory: '/root/libertea/./data/usages/day/2024-05-07.json' [Errno 2] No such file or directory: '/root/libertea/./data/usages/day/2024-05-08.json' [Errno 2] No such file or directory: '/root/libertea/./data/usages/day/2024-05-09.json' [Errno 2] No such file or directory: '/root/libertea/./data/usages/day/2024-05-10.json' 2024-05-11 04:04:09 - CRON periodic_update_users_stats_786405 - DONE updating users stats cache Sat May 11 04:05:00 2024 - [uwsgi-cron] routing signal 4 Ran command 'certbot certonly --standalone -d xxx.xxxxx.xxx --agree-tos --email info@xxx.xxxxx.xxx--non-interactive --http-01-port 9999' and got exit code 256