[GH-ISSUE #1560] Modoboa installed, but no site reachable #1226

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

Originally created by @JDittmerCOM on GitHub (Aug 30, 2018).
Original GitHub issue: https://github.com/modoboa/modoboa/issues/1560

Impacted versions

  • Modoboa: latest Master version
  • installer used: Yes
  • Webserver: Apache

I installed everything after the instructions, but now my whole server does not work anymore.
I have the message "Internal Server Error" on every page.

I hope you can help me very quickly.

And these are the most recent errors from the log file.
https://pastebin.com/KH2G0piD

Originally created by @JDittmerCOM on GitHub (Aug 30, 2018). Original GitHub issue: https://github.com/modoboa/modoboa/issues/1560 # Impacted versions * Modoboa: latest Master version * installer used: Yes * Webserver: Apache I installed everything after the instructions, but now my whole server does not work anymore. I have the message "Internal Server Error" on every page. I hope you can help me very quickly. And these are the most recent errors from the log file. https://pastebin.com/KH2G0piD
kerem closed this issue 2026-02-27 11:15:58 +03:00
Author
Owner

@tonioo commented on GitHub (Aug 30, 2018):

Did you install Modoboa manually?

On 30/08/2018 20:06, Justin Dittmer wrote:

Impacted versions

  • Modoboa: latest Master version
  • installer used: Yes
  • Webserver: Apache

I installed everything after the instructions, but now my whole server
does not work anymore.
I have the message "Internal Server Error" on every page.

I hope you can help me very quickly.

And these are the most recent errors from the log file.
|Aug 30 20:02:57 euve263467 postfix/pickup[1702]: 1E85481E8F: uid=0
from= Aug 30 20:02:57 euve263467 postfix/cleanup[11796]:
warning: connect to Milter service inet:127.0.0.1:12345: Connection
refused Aug 30 20:02:57 euve263467 postfix/cleanup[11796]: warning:
proxy:mysql:/etc/postfix/sql-aliases.cf lookup error for
"root@mail.ets2money.com" Aug 30 20:02:57 euve263467
postfix/cleanup[11796]: warning: 1E85481E8F: virtual_alias_maps map
lookup problem for root@mail.ets2money.com -- message not accepted,
try again later Aug 30 20:02:58 euve263467 postfix/master[1697]:
warning: unix_trigger_event: read timeout for service public/pickup
Aug 30 20:02:58 euve263467 postfix/pickup[1702]: 1F09981E8F: uid=118
from= Aug 30 20:02:58 euve263467 postfix/cleanup[11660]:
warning: connect to Milter service inet:127.0.0.1:12345: Connection
refused Aug 30 20:02:58 euve263467 postfix/cleanup[11660]: warning:
proxy:mysql:/etc/postfix/sql-aliases.cf lookup error for
"opendkim@mail.ets2money.com" Aug 30 20:02:58 euve263467
postfix/cleanup[11660]: warning: 1F09981E8F: virtual_alias_maps map
lookup problem for opendkim@mail.ets2money.com -- message not
accepted, try again later Aug 30 20:02:59 euve263467
postfix/pickup[1702]: 1F87381E8F: uid=1005 from= Aug 30
20:02:59 euve263467 postfix/cleanup[11796]: warning: connect to Milter
service inet:127.0.0.1:12345: Connection refused Aug 30 20:02:59
euve263467 postfix/cleanup[11796]: warning:
proxy:mysql:/etc/postfix/sql-aliases.cf lookup error for
"vmail@mail.ets2money.com" Aug 30 20:02:59 euve263467
postfix/cleanup[11796]: warning: 1F87381E8F: virtual_alias_maps map
lookup problem for vmail@mail.ets2money.com -- message not accepted,
try again later|


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/modoboa/modoboa/issues/1560, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAgc7jjIvbkNcJEx7COMCIH7RMiIPXffks5uWCm9gaJpZM4WT9RT.

<!-- gh-comment-id:417417222 --> @tonioo commented on GitHub (Aug 30, 2018): Did you install Modoboa manually? On 30/08/2018 20:06, Justin Dittmer wrote: > > > Impacted versions > > * Modoboa: latest Master version > * installer used: Yes > * Webserver: Apache > > I installed everything after the instructions, but now my whole server > does not work anymore. > I have the message "Internal Server Error" on every page. > > I hope you can help me very quickly. > > And these are the most recent errors from the log file. > |Aug 30 20:02:57 euve263467 postfix/pickup[1702]: 1E85481E8F: uid=0 > from=<root> Aug 30 20:02:57 euve263467 postfix/cleanup[11796]: > warning: connect to Milter service inet:127.0.0.1:12345: Connection > refused Aug 30 20:02:57 euve263467 postfix/cleanup[11796]: warning: > proxy:mysql:/etc/postfix/sql-aliases.cf lookup error for > "root@mail.ets2money.com" Aug 30 20:02:57 euve263467 > postfix/cleanup[11796]: warning: 1E85481E8F: virtual_alias_maps map > lookup problem for root@mail.ets2money.com -- message not accepted, > try again later Aug 30 20:02:58 euve263467 postfix/master[1697]: > warning: unix_trigger_event: read timeout for service public/pickup > Aug 30 20:02:58 euve263467 postfix/pickup[1702]: 1F09981E8F: uid=118 > from=<opendkim> Aug 30 20:02:58 euve263467 postfix/cleanup[11660]: > warning: connect to Milter service inet:127.0.0.1:12345: Connection > refused Aug 30 20:02:58 euve263467 postfix/cleanup[11660]: warning: > proxy:mysql:/etc/postfix/sql-aliases.cf lookup error for > "opendkim@mail.ets2money.com" Aug 30 20:02:58 euve263467 > postfix/cleanup[11660]: warning: 1F09981E8F: virtual_alias_maps map > lookup problem for opendkim@mail.ets2money.com -- message not > accepted, try again later Aug 30 20:02:59 euve263467 > postfix/pickup[1702]: 1F87381E8F: uid=1005 from=<vmail> Aug 30 > 20:02:59 euve263467 postfix/cleanup[11796]: warning: connect to Milter > service inet:127.0.0.1:12345: Connection refused Aug 30 20:02:59 > euve263467 postfix/cleanup[11796]: warning: > proxy:mysql:/etc/postfix/sql-aliases.cf lookup error for > "vmail@mail.ets2money.com" Aug 30 20:02:59 euve263467 > postfix/cleanup[11796]: warning: 1F87381E8F: virtual_alias_maps map > lookup problem for vmail@mail.ets2money.com -- message not accepted, > try again later| > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/modoboa/modoboa/issues/1560>, or mute the thread > <https://github.com/notifications/unsubscribe-auth/AAgc7jjIvbkNcJEx7COMCIH7RMiIPXffks5uWCm9gaJpZM4WT9RT>. >
Author
Owner

@JDittmerCOM commented on GitHub (Aug 30, 2018):

These was my install steps:

  1. cd /tmp
  2. wget https://github.com/modoboa/modoboa-installer/archive/master.zip
  3. unzip master.zip
  4. rm master.zip
  5. cd modoboa-installer-master/
  6. ./run.py --stop-after-configfile-check ets2money.com
  7. nano installer.cfg and have change the mail address for letsencrypt and root password mysql
  8. ./run.py ets2money.com

Since then all my pages are down on the server.

<!-- gh-comment-id:417418669 --> @JDittmerCOM commented on GitHub (Aug 30, 2018): These was my install steps: 1. cd /tmp 2. wget https://github.com/modoboa/modoboa-installer/archive/master.zip 3. unzip master.zip 4. rm master.zip 5. cd modoboa-installer-master/ 6. ./run.py --stop-after-configfile-check ets2money.com 7. nano installer.cfg and have change the mail address for letsencrypt and root password mysql 8. ./run.py ets2money.com Since then all my pages are down on the server.
Author
Owner

@tonioo commented on GitHub (Aug 31, 2018):

And what about Apache? Did you install it manually after that?

To display more information, edit the settings.py file, set the DEBUG variable to True and reload apache.

<!-- gh-comment-id:417715272 --> @tonioo commented on GitHub (Aug 31, 2018): And what about Apache? Did you install it manually after that? To display more information, edit the settings.py file, set the DEBUG variable to True and reload apache.
Author
Owner

@tonioo commented on GitHub (Sep 11, 2018):

@JDittmerCOM Any news?

<!-- gh-comment-id:420244726 --> @tonioo commented on GitHub (Sep 11, 2018): @JDittmerCOM Any news?
Author
Owner

@UOCecalero commented on GitHub (Feb 13, 2019):

Same issue here. Could you share the solution? Thx

<!-- gh-comment-id:463344287 --> @UOCecalero commented on GitHub (Feb 13, 2019): Same issue here. Could you share the solution? Thx
Author
Owner

@UOCecalero commented on GitHub (Feb 13, 2019):

Feb 13 19:56:08 mail postfix/cleanup[12263]: warning: connect to Milter service inet:127.0.0.1:12345: Connection refused
Feb 13 19:56:08 mail postfix/proxymap[6770]: warning: mysql:/etc/postfix/sql-aliases.cf is unavailable. open /etc/postfix/sql-aliases.cf: No such file or directory
Feb 13 19:56:08 mail postfix/cleanup[12263]: warning: proxy:mysql:/etc/postfix/sql-aliases.cf lookup error for "root@mail.*"
Feb 13 19:56:08 mail postfix/cleanup[12263]: warning: 0119A4C6C9: virtual_alias_maps map lookup problem for root@mail.
-- message not accepted, try again later

<!-- gh-comment-id:463344871 --> @UOCecalero commented on GitHub (Feb 13, 2019): Feb 13 19:56:08 mail postfix/cleanup[12263]: warning: connect to Milter service inet:127.0.0.1:12345: Connection refused Feb 13 19:56:08 mail postfix/proxymap[6770]: warning: mysql:/etc/postfix/sql-aliases.cf is unavailable. open /etc/postfix/sql-aliases.cf: No such file or directory Feb 13 19:56:08 mail postfix/cleanup[12263]: warning: proxy:mysql:/etc/postfix/sql-aliases.cf lookup error for "root@mail.*******" Feb 13 19:56:08 mail postfix/cleanup[12263]: warning: 0119A4C6C9: virtual_alias_maps map lookup problem for root@mail.****** -- message not accepted, try again later
Author
Owner

@UOCecalero commented on GitHub (Feb 13, 2019):

Feb 13 19:39:39 mail dovecot: auth-worker(10120): Error: mysql(127.0.0.1): Connect failed to database (modoboa): Can't connect to MySQL server on '127.0.0.1' (111) - waiting for 125 seconds before retry

<!-- gh-comment-id:463345670 --> @UOCecalero commented on GitHub (Feb 13, 2019): Feb 13 19:39:39 mail dovecot: auth-worker(10120): Error: mysql(127.0.0.1): Connect failed to database (modoboa): Can't connect to MySQL server on '127.0.0.1' (111) - waiting for 125 seconds before retry
Author
Owner

@UOCecalero commented on GitHub (Feb 13, 2019):

I tried to connect to my database but throw me this error:

ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2 "No such file or directory")

(MYSQL worked fine before the installation)

<!-- gh-comment-id:463346059 --> @UOCecalero commented on GitHub (Feb 13, 2019): I tried to connect to my database but throw me this error: ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2 "No such file or directory") (MYSQL worked fine before the installation)
Author
Owner

@DaveDischord commented on GitHub (May 29, 2019):

Running into similar issue

<!-- gh-comment-id:496930371 --> @DaveDischord commented on GitHub (May 29, 2019): Running into similar issue
Author
Owner

@DaveDischord commented on GitHub (May 29, 2019):

After a bit of searching, I did 2 things. My issue is resolved, but I don't know which of either, or both, did the trick. First, I noticed "localhost" wasn't in my /etc/hosts file, just the local IP joined with my server hostnames, so I added
127.0.0.1 localhost
Second, I ran
sudo nano /etc/default/opendkim
and changed
SOCKET="inet:12345@localhost"
to
SOCKET="inet:12345@127.0.0.1
I restarted after that, and if opendkim FAILED on startup, I can start it manually and it works out, web admin pages come up, and everything works as well as I'm aware. Hope that helps.

<!-- gh-comment-id:497054768 --> @DaveDischord commented on GitHub (May 29, 2019): After a bit of searching, I did 2 things. My issue is resolved, but I don't know which of either, or both, did the trick. First, I noticed "localhost" wasn't in my **/etc/hosts** file, just the local IP joined with my server hostnames, so I added `127.0.0.1 localhost` Second, I ran `sudo nano /etc/default/opendkim` and changed `SOCKET="inet:12345@localhost"` to `SOCKET="inet:12345@127.0.0.1` I restarted after that, and if opendkim FAILED on startup, I can start it manually and it works out, web admin pages come up, and everything works as well as I'm aware. Hope that helps.
Author
Owner

@acecconato commented on GitHub (Jan 30, 2021):

Same issue for me on a fresh installation and Debian 9, I either don't' know where is this settings.py

<!-- gh-comment-id:770284005 --> @acecconato commented on GitHub (Jan 30, 2021): Same issue for me on a fresh installation and Debian 9, I either don't' know where is this settings.py
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#1226
No description provided.