[GH-ISSUE #1519] It's can't use letsencrypt if web server change port. #1195

Closed
opened 2026-02-27 11:15:48 +03:00 by kerem · 3 comments
Owner

Originally created by @akong77 on GitHub (Jul 9, 2018).
Original GitHub issue: https://github.com/modoboa/modoboa/issues/1519

Impacted versions

  • Modoboa: 1.10.5
  • installer used: Yes/No ? Yes
  • Webserver: Nginx

Steps to reproduce

I change installer.cfg to letsencrypt.I also change modoboa.conf.tpl with 80 port to 82 port and 443 port to 8443 port.Then I run "./run.py mydomain".It's can run to finish.But nginx can't start.If I change installer.cfg to self-signed and use 82 port and 8443 port.The nginx will running.Could letsencrypt not support change web server port?

Current behavior

Expected behavior

Video/Screenshot link (optional)

Originally created by @akong77 on GitHub (Jul 9, 2018). Original GitHub issue: https://github.com/modoboa/modoboa/issues/1519 # Impacted versions * Modoboa: 1.10.5 * installer used: Yes/No ? Yes * Webserver: Nginx # Steps to reproduce I change installer.cfg to letsencrypt.I also change modoboa.conf.tpl with 80 port to 82 port and 443 port to 8443 port.Then I run "./run.py mydomain".It's can run to finish.But nginx can't start.If I change installer.cfg to self-signed and use 82 port and 8443 port.The nginx will running.Could letsencrypt not support change web server port? # Current behavior # Expected behavior # Video/Screenshot link (optional)
kerem 2026-02-27 11:15:48 +03:00
Author
Owner

@tonioo commented on GitHub (Jul 9, 2018):

The LE script is running using the standalone mode, ie. it does not use nginx so it should work, unless the 80/443 ports are already used. Can you provide the output of the installer using the --debug option?

<!-- gh-comment-id:403532039 --> @tonioo commented on GitHub (Jul 9, 2018): The LE script is running using the standalone mode, ie. it does not use nginx so it should work, unless the 80/443 ports are already used. Can you provide the output of the installer using the --debug option?
Author
Owner

@akong77 commented on GitHub (Jul 10, 2018):

I know what's problem.Because letsencrypt need upload file to web server.And letsencrypt only upload to 80 port web server.So it's will direct auth http://mail.domain.tld/.well-known/acme-challenge/random_code. But the path it's not my modoboa server.This is my another web server.How to fix it?

<!-- gh-comment-id:403678521 --> @akong77 commented on GitHub (Jul 10, 2018): I know what's problem.Because letsencrypt need upload file to web server.And letsencrypt only upload to 80 port web server.So it's will direct auth http://mail.domain.tld/.well-known/acme-challenge/random_code. But the path it's not my modoboa server.This is my another web server.How to fix it?
Author
Owner

@tonioo commented on GitHub (Jul 10, 2018):

That's not a modoboa issue. I suggest you add a redirect rule to the web server running on port 80 so requests sent to http://mail.domain.tld/.well-known/acme-challenge/random_code are redirected to the right server.

<!-- gh-comment-id:403766019 --> @tonioo commented on GitHub (Jul 10, 2018): That's not a modoboa issue. I suggest you add a redirect rule to the web server running on port 80 so requests sent to http://mail.domain.tld/.well-known/acme-challenge/random_code are redirected to the right server.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/modoboa-modoboa#1195
No description provided.