mirror of
https://github.com/modoboa/modoboa.git
synced 2026-04-26 01:16:01 +03:00
[GH-ISSUE #1080] Bad request (HTTP 400) #902
Labels
No labels
bug
bug
dependencies
design
documentation
duplicate
enhancement
enhancement
enhancement
feedback-needed
help-needed
help-needed
installer
invalid
looking-for-sponsors
modoboa-contacts
new-ui
new-ui
pr
pull-request
pyconfr
python
question
security
stale
webmail
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/modoboa-modoboa#902
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @PeterBocan on GitHub (Mar 17, 2017).
Original GitHub issue: https://github.com/modoboa/modoboa/issues/1080
Impacted versions
Latest (using Installer)
Steps to reproduce
Installed Modoboa using installer. I ran
./run.py mail.pbocan.netwhich was bad (it has prepended the mail part again) so I had to fix some duplicates in NGINX configuration (already had SSL set up) after that, I had to fix the names of the subdomain and so on.I know a thing that may be breaking the code: /tmp is not mounted (at all) with /noexec flag. (I am running on VPS)
Current behavior
Reaching the frontend of the mail administration responds with HTTP 400 (Bad request)
Expected behavior
Display the login screen
Video/Screenshot link (optional)
@PeterBocan commented on GitHub (Mar 17, 2017):
Can I/Should I rerun the installer?
@tonioo commented on GitHub (Mar 17, 2017):
@PeterBocan When did you run the installer?
@PeterBocan commented on GitHub (Mar 17, 2017):
today.
@tonioo commented on GitHub (Mar 17, 2017):
Ok, so now the right way to run the installer is:
Please try to run the installer once again.
@PeterBocan commented on GitHub (Mar 17, 2017):
Do I have to edit the installer.cfg first? It seems like I should set at least the usernames and passwords right?
@tonioo commented on GitHub (Mar 17, 2017):
yes, add default values are 'password'.
@PeterBocan commented on GitHub (Mar 17, 2017):
Okay, now I get Internal Server Error. Do I need to create mysql user manually? And/or what should I check?
It did not generate the let's encrypt certificate. Have to check it manually: It could not paste ACME challenge into the root of the website.
@tonioo commented on GitHub (Mar 17, 2017):
No, it should be created by the installer. Can you set DEBUG to True inside /srv/modoboa/instance/instance/settings.py, reload uwsgi and retry please?
@PeterBocan commented on GitHub (Mar 17, 2017):
now I can't even load webpage. ERR_CONNECTION_RESET or ERR_CONNECTION_CLOSED. Dammit.
EDIT: My bad, I have commented out nonexistent paths to certificates.
@tonioo commented on GitHub (Mar 21, 2017):
@PeterBocan Is your problem fixed now?
@PeterBocan commented on GitHub (Mar 21, 2017):
No, I haven't solved it yet. I may install the certificate as a root at first time and then I hope it will renew the certificate by itself.
@flyncos commented on GitHub (Apr 1, 2017):
I have the same problem, I did no changes to the installer settings and I just ran
./run.py mysite.com, I get a ERR_CONNECTION_CLOSED and log files are empty with debug enabled.@PeterBocan commented on GitHub (Apr 1, 2017):
You most likely don't have SSL certs.
@flyncos commented on GitHub (Apr 1, 2017):
@PeterBocan No, the certs are there and ok
@flyncos commented on GitHub (Apr 2, 2017):
Fixed by me, I had wrong permissions on the uwsgi socket and forgot to add the reverse entry in the /etc/hosts file
121.21.xx.xx mail.pbocan.net@lazynooblet commented on GitHub (Apr 15, 2017):
FYI this also occurs if you mispell the hostname during "deploy" command
@tonioo commented on GitHub (Jun 1, 2017):
@PeterBocan Any news about this? Looks like this issue is more related to the installer than to modoboa.
@PeterBocan commented on GitHub (Jun 1, 2017):
Havent had time to look at that yet.
@mylastore commented on GitHub (Sep 5, 2017):
I had the same problem Bad request (HTTP 400) wen't to sleep and the next day everything was install correctly seems the it takes time for the domain propagation to take place. I could not fine any documentation on how to set your domain DNS settings or there is no need to have any custom DNS records.
@PeterBocan commented on GitHub (Sep 5, 2017):
@mylastore I went for AWS WebMail and they said on their site, that it will take 3 days to propagate change DNS globally, which turned up to be true actually.