-
-
Notifications
You must be signed in to change notification settings - Fork 127
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
Nextcloud not fully loading in Edge, Chrome works - related somehow to default.conf #402
Comments
I am facing a similar issue on Firefox, albeit I am having far less of the page load than you seem to. Removing those lines seems to only resolve the issue for me if I also spoof my user agent to Chrome. |
I saw that issue a while ago. |
same issue,had to revert those changes to get nextcloud properly work |
we have a PR being confirmed now to resolve this. applies to #403 also |
@drizuid |
can you provide full container logs please note i need the container logs before you made changes/commented things |
This one?
|
yep, and this is using the new site-confs/default.conf as shipped, with no changes? |
Yes, I copied the default.conf.sample to default.conf to overwrite my adaptations and additionally re-created the container. |
ok, thanks! give us a bit |
just to be sure, after you copied the sample to default.conf, did you restart the container for the change to take effect? |
Yes, I restarted the container. And by the way, the logviewer page in Nextcloud stays empty and doesn´t show anything. This worked in between after it has been fixed by the update to 28.0.1 and the new container. |
i can replicate the issue and i am working on a PR |
Great! Thanks a lot. |
mr pr is here, but isn't covering all the issues yet. you're still welcome to play with it. #405 |
hi guys, please test |
Great job! It works again. With Chrome, Edge as well as the Nextcloud logging page. Thank you. |
sorry for any inconvenience, we caught a couple inconsistencies that have been resolved now. do you mind testing |
I quickly tested It is somehow really strange. In principle Nextcloud works. But the logging page of Nextcloud now properly works in Edge whereas it doesn´t show anything in Chrome. |
Just for completeness. I´m not sure if I tested the logging page with the previous versions on both browsers. I could test it this evening or tomorrow if required. The next hours I´m not available. |
@drizuid : Can you reproduce that the logging page is blank with Chrome whereas it shows it in Edge? |
I can reproduce the logging page being blank in chrome when I have adblock (ublock origin lite) enabled 😄 It works as expected with adblock disabled though. |
i use pihole, without making any adjustments to it, i can access the logging page fine |
I´m not aware of any ad-blocker and haven´t found one in the extensions. Anyhow, you might be right. On my mobile phone it shows up in Chrome. Thanks a lot for your support. |
Is there an existing issue for this?
Current Behavior
I upgraded Nextcloud from 27.X to 28.0.1.1 with the latest Docker release build and replaced the default.conf by the newly provided default.conf.sample.
Whereas in Chrom Nextcloud works properly, it doesn´t fully load in Edge. It starts that on the login page that it shows "Anmelden bei {productName}" instead of "Anmelden bei Nextcloud". After loging in and showing the Dashboard, it is neither able to load the files, nor the mails or weather. When switching to the Files App, it doesn´t show any files. In the development sidebar of Edge, a lot "..404 (Not Found)" errors are shown.
Expected Behavior
It should work in Edge as in Chrome
Steps To Reproduce
After playing around a bit and trying out different things, I found that it works again when removing the following (new) part of the default.conf below "location ~ .(?:css|js|mjs|svg|gif|png|jpg|ico|wasm|tflite|map|ogg|flac)$ {":
Whether the above is just a (not proper workaround) for resolving the actual problem or really the solutions, I don´t know.
Environment
CPU architecture
x86-64
Docker creation
![image](https://github.com/linuxserver/docker-nextcloud/assets/44039580/e9bf3398-dfa0-4b98-a421-85a81e9bb3cf)
Container logs
The text was updated successfully, but these errors were encountered: