mirror of
https://github.com/modoboa/modoboa.git
synced 2026-04-25 00:46:03 +03:00
[GH-ISSUE #3279] An internal error occured. #1825
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#1825
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 @Jossyboydgenius on GitHub (Jul 30, 2024).
Original GitHub issue: https://github.com/modoboa/modoboa/issues/3279
Impacted versions
Current behavior
Sorry
An internal error occurred.
Expected behavior
I should be able to log in to my dashboard.
Screenshot link (optional)
@jarforce commented on GitHub (Aug 5, 2024):
It should be related to module "'modoboa_postfix_autoreply"
to workaround in case waiting for a fix solutions, we could be disable"
#'modoboa.postfix_autoreply',
#'modoboa_postfix_autoreply',
and manual run migrate again
please noted that installer scripts can not fix this issue automatic until now
@VladislavGatsenko commented on GitHub (Aug 10, 2024):
same error
@Jossyboydgenius commented on GitHub (Aug 17, 2024):
Thanks @jarforce
@pekidi commented on GitHub (Aug 23, 2024):
the exact problem here
upgrade to 2.3.1 i got Server internal error
How to repair it.
@alekso56 commented on GitHub (Aug 25, 2024):
Edit:
Fixed by
Original message;
@pekidi commented on GitHub (Aug 26, 2024):
I managed to solve upgrade with:
git clone https://github.com/modoboa/modoboa-installer.git
cp old installer.cfg file to a new one modoboa-installer folder
and run:
./run.py --upgrade "domain"
and now it is fine
@stale[bot] commented on GitHub (Jan 31, 2025):
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.