[GH-ISSUE #85] Creating bookmark on the server failed, but it didn't fail

kerem commented

2026-02-25 22:36:05 +03:00

Owner

Originally created by @TheDevFreak on GitHub (Apr 15, 2018).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/85

Software versions

Browser: FF60.0
Nextcloud: 13.0.1
Nextcloud Bookmarks app: 0.11.0
Floccus: 2.0.6

Steps to reproduce

Remove bookmark from server
Create bookmark on client
Press Sync

Expected outcome

Sync successful message

Actual outcome

A good few "Creating bookmark on the server failed" messages, despite bookmarks actually being added the the server

Originally created by @TheDevFreak on GitHub (Apr 15, 2018). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/85  ### Software versions  * Browser: FF60.0 * Nextcloud: 13.0.1 * Nextcloud Bookmarks app: 0.11.0 * Floccus: 2.0.6 ### Steps to reproduce  1. Remove bookmark from server 2. Create bookmark on client 3. Press Sync ### Expected outcome  Sync successful message ### Actual outcome  A good few "Creating bookmark on the server failed" messages, despite bookmarks actually being added the the server

kerem closed this issue

2026-02-25 22:36:05 +03:00

kerem commented

2026-02-25 22:36:05 +03:00

Author

Owner

@TheDevFreak commented on GitHub (Apr 15, 2018):

False alarm, it's due to a reverse proxy configuration. Temporary fix is disabling brute force protection

@TheDevFreak commented on GitHub (Apr 15, 2018): False alarm, it's due to a reverse proxy configuration. Temporary fix is disabling brute force protection

kerem commented

2026-02-25 22:36:05 +03:00

Author

Owner

@mobamoba commented on GitHub (Apr 28, 2018):

I'd like to reopen this as running Nextcloud behind an Nginx reverse proxy causes this problem. No clue why as every other aspect of Nextcloud works fine behind the reverse proxy. How could we debug this as it's not an option for me to run Nextcloud without Nginx and Floccus is the only app that doesn't work with it? Thanks.

@mobamoba commented on GitHub (Apr 28, 2018): I'd like to reopen this as running Nextcloud behind an Nginx reverse proxy causes this problem. No clue why as every other aspect of Nextcloud works fine behind the reverse proxy. How could we debug this as it's not an option for me to run Nextcloud without Nginx and Floccus is the only app that doesn't work with it? Thanks.

kerem commented

2026-02-25 22:36:06 +03:00

Author

Owner

@marcelklehr commented on GitHub (Apr 28, 2018):

@mobamoba I take it you've tried disabling brute force protection? Mmh. It would be interesting to see the reply from the server. Could you debug floccus and inspect the HTTP request that tries to create the bookmark in the network panel of the debugger?

@marcelklehr commented on GitHub (Apr 28, 2018): @mobamoba I take it you've tried disabling brute force protection? Mmh. It would be interesting to see the reply from the server. Could you debug floccus and inspect the HTTP request that tries to create the bookmark in the network panel of the debugger?

kerem commented

2026-02-25 22:36:06 +03:00

Author

Owner

@mobamoba commented on GitHub (Apr 28, 2018):

It just gives a bunch of 504 Gateway Timeouts. I'm actually accessing my Nextcloud instance at the time Floccus is saying the gateway is timing out. The url it's using is correct - https://my.nextcloud.com:nginxport/index.php/apps/bookmarks/public/rest/v2/bookmark

Same thing happens in Chrome if that helps. When I switch it to the non-Nginx connection, it all syncs fine.

@mobamoba commented on GitHub (Apr 28, 2018): It just gives a bunch of 504 Gateway Timeouts. I'm actually accessing my Nextcloud instance at the time Floccus is saying the gateway is timing out. The url it's using is correct - https://my.nextcloud.com:nginxport/index.php/apps/bookmarks/public/rest/v2/bookmark Same thing happens in Chrome if that helps. When I switch it to the non-Nginx connection, it all syncs fine.

kerem commented

2026-02-25 22:36:06 +03:00

Author

Owner

@marcelklehr commented on GitHub (Apr 28, 2018):

Then it might be because the bookmarks app fetches the web pages you create bookmarks for. Can you increase the timeout in nginx?

@marcelklehr commented on GitHub (Apr 28, 2018): Then it might be because the bookmarks app fetches the web pages you create bookmarks for. Can you increase the timeout in nginx?

kerem commented

2026-02-25 22:36:06 +03:00

Author

Owner

@mobamoba commented on GitHub (Apr 28, 2018):

That made no difference.

@mobamoba commented on GitHub (Apr 28, 2018): That made no difference.

kerem commented

2026-02-25 22:36:06 +03:00

Author

Owner

@mobamoba commented on GitHub (Apr 29, 2018):

Okay after a bunch of trial and error, here's what works for me at least with Floccus and Nextcloud - I'm don't really know enough about Nginx to know which part of this is the necessary part for Floccus but all is working now so I'm posting in case someone else has this issue:

`location /{
proxy_pass http://NEXTCLOUD/;
proxy_buffering off;
proxy_http_version 1.1;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;
proxy_request_buffering off;
client_max_body_size 0;
proxy_read_timeout 36000s;
proxy_ssl_session_reuse off;

}`

@mobamoba commented on GitHub (Apr 29, 2018): Okay after a bunch of trial and error, here's what works for me at least with Floccus and Nextcloud - I'm don't really know enough about Nginx to know which part of this is the necessary part for Floccus but all is working now so I'm posting in case someone else has this issue: > `location /{ proxy_pass http://NEXTCLOUD/; proxy_buffering off; proxy_http_version 1.1; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $http_connection; proxy_request_buffering off; client_max_body_size 0; proxy_read_timeout 36000s; proxy_ssl_session_reuse off; }`

kerem commented

2026-02-25 22:36:06 +03:00

Author

Owner

@bfayers commented on GitHub (Apr 30, 2018):

When I resolved this for myself I did this https://github.com/nextcloud/docker/issues/294#issuecomment-381418214 but im running through a reverse proxy, all this did was ensured nextcloud new of the correct IP which in turn made disabling bruteforce protection not be needed. So i know have functioning IPs inside the container and bruteforce protection on

@bfayers commented on GitHub (Apr 30, 2018): When I resolved this for myself I did this https://github.com/nextcloud/docker/issues/294#issuecomment-381418214 but im running through a reverse proxy, all this did was ensured nextcloud new of the correct IP which in turn made disabling bruteforce protection not be needed. So i know have functioning IPs inside the container and bruteforce protection on

kerem commented

2026-02-25 22:36:06 +03:00

Author

Owner

@bhlevca commented on GitHub (Mar 3, 2019):

One year later and I have the same problem. With nextcloud behind haproxy floccus cannot connect.
Everything else works fine. I tried all the suggestion form above . I don't have the brute force app , but I use fail2ban instead.
My nextcloud server runs in virtual domain of an apache2 server and it is difficult for me to connect directly to that apache virtual domain using the IP.

Is there any way to debug this i looked in haproxy.logs and in the nextcloud logsand I found nothing relevant.

Thanks

@bhlevca commented on GitHub (Mar 3, 2019): One year later and I have the same problem. With nextcloud behind haproxy floccus cannot connect. Everything else works fine. I tried all the suggestion form above . I don't have the brute force app , but I use fail2ban instead. My nextcloud server runs in virtual domain of an apache2 server and it is difficult for me to connect directly to that apache virtual domain using the IP. Is there any way to debug this i looked in haproxy.logs and in the nextcloud logsand I found nothing relevant. Thanks

kerem commented

2026-02-25 22:36:06 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 21, 2023):

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions[bot] commented on GitHub (Mar 21, 2023): This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

Rows
Columns

[GH-ISSUE #85] Creating bookmark on the server failed, but it didn't fail #84

Software versions

Steps to reproduce

Expected outcome

Actual outcome