Skip to content
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.

Sign up for GitHub

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

Jump to bottom

hub using non-existant cache for css #1261

Closed
mark-hahn opened this issue Jun 2, 2015 · 2 comments
Closed

hub using non-existant cache for css #1261

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

Comments

@mark-hahn
Copy link

(this was previously in #1257)

I've got nginx https working. Now I'm having a problem with the https://mydomain.com 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.

https://mydomain.com/media/CACHE/css/999e7b4d6bb4.css

This is causing my page to look like ...

screenshot 2015-06-01 at 7 35 35 pm

Edit: This url works fine ...

https://hahnca.com/sys/useradmin/

Also, I have reinstalled seafile and this still happens.

Edit2: I have also tried clearing my browser cache.
@andi-blafasl
Copy link

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

@mark-hahn
Copy link
Author

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 reopened this Jun 3, 2015
@galvanopus galvanopus mentioned this issue Oct 25, 2015
Closed
0x64746b added a commit to 0x64746b/seafile-server-installer that referenced this issue Feb 5, 2016
@0x64746b
Remove /tmp/seahub_cache on uninstall
e8d84f8 
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.
@0x64746b 0x64746b mentioned this issue Feb 5, 2016
Merged
@TexasDex TexasDex mentioned this issue Sep 15, 2016
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mark-hahn @andi-blafasl