search

hakwerk / labca

A private Certificate Authority for internal (lab) use, based on the open source ACME Automated Certificate Management Environment implementation from Let's Encrypt (tm).
https://lab-ca.net
Other
374 stars 39 forks source link

Error when testing email #112

Closed jon2100 closed 8 months ago

jon2100 commented 9 months ago

When setting up the email config and trying to verify, clicking on the "Send Test Email" returns "Internal Server Error", looking at the logs from the container labca-gui1.

2024/02/15 18:25:00 POST /manage 2024/02/15 18:25:00 ERROR: Message from server: '2024-02-15T18:25:00.813669+00:00Z mail-tester[898]: 6 mail-tester mr-umAU Debug server listening on :8008 2024-02-15T18:25:00.814024+00:00Z mail-tester[898]: 6 mail-tester j-K1-Q0 Versions: mail-tester=(Unspecified Unspecified) Golang=(go1.21.5) BuildHost=(Unspecified) 2024-02-15T18:25:00.816475+00:00Z mail-tester[898]: 3 mail-tester 8Izp5QI [AUDIT] unable to boot debug server on :8008: listen tcp :8008: bind: address already in use ERROR! On line 170 in commander script ' 2024/02/15 18:25:00 errorHandler: err=2024-02-15T18:25:00.813669+00:00Z mail-tester[898]: 6 mail-tester mr-umAU Debug server listening on :8008 2024-02-15T18:25:00.814024+00:00Z mail-tester[898]: 6 mail-tester j-K1-Q0 Versions: mail-tester=(Unspecified Unspecified) Golang=(go1.21.5) BuildHost=(Unspecified) 2024-02-15T18:25:00.816475+00:00Z mail-tester[898]: 3 mail-tester 8Izp5QI [AUDIT] unable to boot debug server on :8008: listen tcp :8008: bind: address already in use ERROR! On line 170 in commander script

main._hostCommand({0x1398458, 0xc00014a2a0}, 0xc000230c01?, {0xe4f481, 0xa}, {0xc0004b54d8, 0x1, 0xc0004b55c0?}) /go/src/labca/main.go:2264 +0x67a main._emailSendHandler({0x1398458, 0xc00014a2a0}, 0x0?) /go/src/labca/main.go:965 +0xac main._managePostDispatch({0x1398458, 0xc00014a2a0}, 0xe478b6?, {0xc00003b96f, 0xa}) /go/src/labca/main.go:1294 +0x2b2 main._managePost({0x1398458, 0xc00014a2a0}, 0xc000457600) /go/src/labca/main.go:1393 +0x22b main.manageHandler({0x1398458, 0xc00014a2a0}, 0xc000457600) /go/src/labca/main.go:1634 +0x6a net/http.HandlerFunc.ServeHTTP(0xd2cc40?, {0x1398458?, 0xc00014a2a0?}, 0xc00014a2a0?) /usr/local/go/src/net/http/server.go:2136 +0x29 main.authorized.func1({0x1398458, 0xc00014a2a0}, 0xc000457600) /go/src/labca/main.go:3289 +0x337 net/http.HandlerFunc.ServeHTTP(0xc000457500?, {0x1398458?, 0xc00014a2a0?}, 0x1?) /usr/local/go/src/net/http/server.go:2136 +0x29 github.com/gorilla/mux.(Router).ServeHTTP(0xc0001686c0, {0x1398458, 0xc00014a2a0}, 0xc000457200) /root/go/pkg/mod/github.com/gorilla/mux@v1.8.0/mux.go:210 +0x1c5 net/http.serverHandler.ServeHTTP({0x1395d90?}, {0x1398458?, 0xc00014a2a0?}, 0x6?) /usr/local/go/src/net/http/server.go:2938 +0x8e net/http.(conn).serve(0xc00058cf30, {0x139b0f8, 0xc0004867e0}) /usr/local/go/src/net/http/server.go:2009 +0x5f4 created by net/http.(*Server).Serve in goroutine 1 /usr/local/go/src/net/http/server.go:3086 +0x5cb

hakwerk commented 9 months ago

I have no idea what is running on port 8008 inside your labca-boulder-1 docker container, but you can change the port for the expiration-mailer / mail-tester in /home/labca/boulder_labca/config/expiration-mailer.json. Just change port 8008 to 9009 or so there

jon2100 commented 9 months ago

That is the thing nothing is netstat -tunlp Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:22 0.0.0.0: LISTEN 900/sshd: /usr/sbin tcp 0 0 0.0.0.0:80 0.0.0.0: LISTEN 25023/docker-proxy tcp 0 0 0.0.0.0:443 0.0.0.0: LISTEN 25002/docker-proxy tcp 0 0 127.0.0.53:53 0.0.0.0: LISTEN 833/systemd-resolve tcp6 0 0 :::22 ::: LISTEN 900/sshd: /usr/sbin tcp6 0 0 :::80 ::: LISTEN 25029/docker-proxy tcp6 0 0 :::443 ::: LISTEN 25009/docker-proxy udp 0 0 127.0.0.53:53 0.0.0.0: 833/systemd-resolve udp 0 0 192.168.100.198:68 0.0.0.0: 831/systemd-network udp6 0 0 fe80::20c:29ff:fe2a:546 ::: 831/systemd-network

I'll try moving the port

On Thu, Feb 15, 2024 at 1:30 PM Arjan H. @.***> wrote:

I have no idea what is running on port 8008 inside your labca-boulder-1 docker container, but you can change the port for the expiration-mailer / mail-tester in /home/labca/boulder_labca/config/expiration-mailer.json. Just change port 8008 to 9009 or so there

— Reply to this email directly, view it on GitHub https://github.com/hakwerk/labca/issues/112#issuecomment-1947287424, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC2K4J7JHFYRYQ7X4KETJITYTZV4VAVCNFSM6AAAAABDKYKGBWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBXGI4DONBSGQ . You are receiving this because you authored the thread.Message ID: @.***>

jon2100 commented 9 months ago

I have no idea what is running on port 8008 inside your labca-boulder-1 docker container, but you can change the port for the expiration-mailer / mail-tester in /home/labca/boulder_labca/config/expiration-mailer.json. Just change port 8008 to 9009 or so there.

so the 9009 stopped getting that error. I tried 8009, which did not work, but. No, I am getting a failed-to-connect, which is interesting. I can, from the OS, make connections and send test emails through my open relay, and when I set it to send to gmail using the same info in my relay, I get the same errors about " mail-tester failed to connect: 534 5.7.9 Application-specific password required." gsmtp ERROR! On line 170 in commander script" and again from the command line on my host, I can send emails all-day

hakwerk commented 9 months ago

The output of your netstat command shows what is running on the host machine, the conflict is inside the docker container.

The command docker exec labca-boulder-1 ps -ef shows all the processes running inside that container and will show that the boulder-publisher process is using port 8009. Unfortunately the netstat command is not available to determine what is running currently on port 8008 inside.

Also your connectivity issue is from inside the container, not from the host.