mirror of
https://github.com/modoboa/modoboa.git
synced 2026-04-26 01:16:01 +03:00
[GH-ISSUE #1693] new install getting 404 on static content #1331
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#1331
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 @tonyguadagno on GitHub (Mar 7, 2019).
Original GitHub issue: https://github.com/modoboa/modoboa/issues/1693
hi, i just installed a brand new modoboa on a fully patched centos 7 server. i used the automatic install which completed without error. I am trying to get into the admin gui but the css and images are not painting....they are throwing 404's.....
I would appreciate any help in figuring out how to get this working....
thanks in advance!
@tonyguadagno commented on GitHub (Mar 7, 2019):
ok, so i found the nginx logs and see this....why is there a permission issue?
2019/03/07 10:15:25 [crit] 16967#0: *13 stat() "/srv/modoboa/instance/sitestatic/css/modoboa.png" failed (13: Permission denied), client: 192.168.168.205, server: mail.ffusa.com, request: "GET /sitestatic/css/modoboa.png HTTP/1.1", host: "mail.ffusa.com", referrer: "https://mail.ffusa.com/accounts/login/?next=/"@tonyguadagno commented on GitHub (Mar 7, 2019):
ok, so more poking around shows me that this is an selinux issue.....and i think this is caused by the fact that modoboa chose to put its web home directory in a non standard path (/srv/modoboa/instance). i was able to find these commands and it seems to have fixed the issue...it seems these should be included in the installer?
@tonyguadagno commented on GitHub (Mar 7, 2019):
update: as it turns out, there are MANY other SELinux violations that get in the way of this working right....regrettable, i had to disable selinux. I don't like doing this, but i don't have enough knowledge to fix all of it....
If anyone knows all the SELinux changes that need to happen, I would appreciate it, it would be nice if the install script could take care of this.
thanks
@cremesk commented on GitHub (Mar 7, 2019):
you can check this: Issue 198
@tonyguadagno commented on GitHub (Mar 7, 2019):
cremesk...GREAT, THANKS, I will try this!