New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

hub using non-existant cache for css #1261

mark-hahn opened this Issue Jun 2, 2015 · 2 comments


None yet
2 participants

mark-hahn commented Jun 2, 2015

(this was previously in #1257)

I've got nginx https working. Now I'm having a problem with the request. It is loading all the files correctly except for one. I am seeing this request get a 404. I checked and there is no CACHE folder in media.

This is causing my page to look like ...

screenshot 2015-06-01 at 7 35 35 pm

Edit: This url works fine ...

Also, I have reinstalled seafile and this still happens.

Edit2: I have also tried clearing my browser cache.


This comment has been minimized.

andi-blafasl commented Jun 3, 2015

I had the same problem when installing a second instance for testing on the same server. I deleted the cache and it seems to fix the problem.

stop seafile server
delete the folder "/tmp/seahub_cache"
start seafile server
clear browser cache and cookies
login again

This comment has been minimized.

mark-hahn commented Jun 3, 2015

That fixed it. Thanks. I had reinstalled several times when chasing problems. Apparently the install did not clear the cache properly.

@mark-hahn mark-hahn closed this Jun 3, 2015

@mark-hahn mark-hahn reopened this Jun 3, 2015

@mark-hahn mark-hahn closed this Jun 3, 2015

0x64746b added a commit to 0x64746b/seafile-server-installer that referenced this issue Feb 5, 2016

Remove `/tmp/seahub_cache` on uninstall
So far the `/media/CACHE` dir wasn't deleted by the uninstaller, which
led to a `404` after a reinstall when requesting the `css` for the
seafile home page. Cf haiwen/seafile#1261.

This commit removes the conflicting directory so that is gets recreated
after a reinstallation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment