Details
-
Bug
-
Resolution: Invalid
-
Major
-
None
-
15.10.5
-
None
-
xwiki ver 15.10.5 using nginx proxy, jetty app server, postgres db, running on debian 12 server
-
Unknown
-
N/A
-
N/A
-
Description
Sorry to bring this up, I know there's been much discussion about it in:
XWIKI-21710
XWIKI-21649
XWIKI-21601
I see that tmortagne has been very active on this problem.
These issues have all been closed as of release 15.10.2 but I clearly have the edit issue and my environment closely matches the environment described in these tickets. I'm using nginx as a proxy and am using the debian / xwiki / jetty / postgres build.
I've been trying to consider what might be different about my setup that would cause 15.10.5 to give the failed to lock error.
Would upgrading to 15.10.5 from 15.10.1 make a difference?
Perhaps my nginx config is incompatible - I'll post it here:
ssl_certificate /etc/letsencrypt/live/example.org/fullchain.pem; # managed by Certbot ssl_certificate_key /etc/letsencrypt/live/example.org/privkey.pem; # managed by Certbot client_max_body_size 100M;
server
{ listen 80 default_server; server_name _; return 301 https://$host$request_uri; }
server {
listen 443 ssl http2 default_server;
server_name example.org www.example.org;
access_log /var/log/xwiki/www-access.log;
error_log /var/log/xwiki/www-error.log;
location = /
{ root /var/www/html; index index.html index.htm; }
}
server {
listen 443 ssl http2;
server_name wiki.example.org;
access_log /var/log/nginx/xwiki-access.log;
error_log /var/log/nginx/xwiki-error.log;
location = /
{ return 301 https://$host/xwiki; }
location /xwiki
{ proxy_set_header X-Real-IP $remote_addr; proxy_set_header Host $host; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection 'upgrade'; proxy_cache_bypass $http_upgrade; proxy_pass http://127.0.0.1:8080/xwiki; }
}
Or perhaps there's a lingering issue still?
Please advise.
Thank you,
-tom
Attachments
Issue Links
- is related to
-
-
- Closed
-