Closed 4Syno closed 1 year ago
Just realized that this happens to me as well and I also cannot revert back to 2.5.2, I get error 400. Wallabag keeps repeting
Package guzzlehttp/ringphp is abandoned, you should avoid using it. No replacement was suggested.
Package guzzlehttp/streams is abandoned, you should avoid using it. No replacement was suggested.
Package hoa/compiler is abandoned, you should avoid using it. No replacement was suggested.
Package hoa/consistency is abandoned, you should avoid using it. No replacement was suggested.
Package hoa/event is abandoned, you should avoid using it. No replacement was suggested.
Package hoa/exception is abandoned, you should avoid using it. No replacement was suggested.
Package hoa/file is abandoned, you should avoid using it. No replacement was suggested.
Package hoa/iterator is abandoned, you should avoid using it. No replacement was suggested.
Package hoa/math is abandoned, you should avoid using it. No replacement was suggested.
Package hoa/protocol is abandoned, you should avoid using it. No replacement was suggested.
Package hoa/regex is abandoned, you should avoid using it. No replacement was suggested.
Package hoa/ruler is abandoned, you should avoid using it. No replacement was suggested.
Package hoa/stream is abandoned, you should avoid using it. No replacement was suggested.
Package hoa/ustring is abandoned, you should avoid using it. No replacement was suggested.
Package hoa/visitor is abandoned, you should avoid using it. No replacement was suggested.
Package hoa/zformat is abandoned, you should avoid using it. No replacement was suggested.
I also have problems with my docker wallabag config after upgrading.
After login the browser is forwarded to https://localhost:7080/login
Here my configs
Docker Wallabag:
docker run -d \ -v /var/dockerstorage/wallabag/data:/var/www/wallabag/data \ -v /var/dockerstorage/wallabag/images:/var/www/wallabag/web/assets/images \ -e SYMFONYENVMAILER_HOST=smtp.... \ -e SYMFONYENVMAILER_USER=myuser \ -e SYMFONYENVMAILER_PASSWORD=mypassword \ -e SYMFONYENVFROM_EMAIL=myemail@... \ -e "SYMFONYENVDOMAIN_NAME=https://myserver:12345" \ --name mswallabag \ --restart=unless-stopped \ -p 127.0.0.1:7080:80 \ wallabag/wallabag
NGINX:
server { listen 12345; ssl on; server_name localhost;
access_log /var/log/nginx/wb-access.log;
error_log /var/log/nginx/wb-error.log;
ssl_certificate /etc/letsencrypt/live/...;
ssl_certificate_key /etc/letsencrypt/live/...;
root /var/www/pages;
client_max_body_size 5M;
index index.html index.htm index.nginx-debian.html;
location / {
proxy_pass http://localhost:7080;
proxy_set_header X-Forwarded-Host $server_name;
proxy_set_header X-Forwarded-Proto https;
proxy_set_header X-Forwarded-For $remote_addr;
}
}
For me there were two working solutions:
proxy_set_header X-Forwarded-Proto https
proxy_redirect https://127.0.0.1:7080/ https://wallabag.server.tld/
(Change ports/server names as needed) to the location block.For the upgrade to 2.6.1 I also needed to migrate the db (see https://github.com/wallabag/wallabag/issues/6649#issuecomment-1616021842)
Thank you! As I made several changes, downloaded again the docker image, ... I do not know what finally worked. My location definition looks like below now: proxy_pass http://127.0.0.1:7080; proxy_set_header Host $host:12345; # <<< maybe this worked(?) proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto https; ... I tried the same config above, and it worked on my raspberry-docker, too.
Thank you, @danielpanteleit, I will give it a try later. As my local host config does work with ssl, I think, it is ok to change "https://127.0.0.1:7080" to "http://127.0.0.1:7080".
...not work...
I'm doing a fresh install, with the added twist of using Podman instead of Docker, and also see this issue with my nginx proxy getting redirected instead of proxied.
As mentioned by @718aba I find adding the Host header helps, though I found adding the port on the container didn't, so:
proxy_set_header Host $host;
I now have a '500 Internal server error' to debug instead. Progress!
[Edit] The server error was fixed by running the database migration command...on a fresh install that seems odd but it's a different issue.
I don't think this is a nginx issue, as nothing changed here, except the docker image of wallabag. it must not return the correct domain on requests, but the proxypass addy.
Oddly downgrading container does not fix it, but then again, not sure which version i ran before. Havent upgraded in a minute.
I also have problems with my docker wallabag config after upgrading.
After login the browser is forwarded to https://localhost:7080/login
Here my configs
Docker Wallabag:
docker run -d -v /var/dockerstorage/wallabag/data:/var/www/wallabag/data -v /var/dockerstorage/wallabag/images:/var/www/wallabag/web/assets/images -e SYMFONYENVMAILER_HOST=smtp.... -e SYMFONYENVMAILER_USER=myuser -e SYMFONYENVMAILER_PASSWORD=mypassword -e SYMFONYENVFROM_EMAIL=myemail@... -e "SYMFONYENVDOMAIN_NAME=https://myserver:12345" --name mswallabag --restart=unless-stopped -p 127.0.0.1:7080:80 wallabag/wallabag
NGINX:
server { listen 12345; ssl on; server_name localhost; #server_name myserver; #Did not work either access_log /var/log/nginx/wb-access.log; error_log /var/log/nginx/wb-error.log; ssl_certificate /etc/letsencrypt/live/...; ssl_certificate_key /etc/letsencrypt/live/...; root /var/www/pages; client_max_body_size 5M; index index.html index.htm index.nginx-debian.html; location / { proxy_pass http://localhost:7080; proxy_set_header X-Forwarded-Host $server_name; proxy_set_header X-Forwarded-Proto https; proxy_set_header X-Forwarded-For $remote_addr; } }
Not related to this issue, but the SMTP settings have been changed, to a one liner. Check the release notes for a few versions back.
I'm doing a fresh install, with the added twist of using Podman instead of Docker, and also see this issue with my nginx proxy getting redirected instead of proxied.
As mentioned by @718aba I find adding the Host header helps, though I found adding the port on the container didn't, so:
proxy_set_header Host $host;
I now have a '500 Internal server error' to debug instead. Progress!
[Edit] The server error was fixed by running the database migration command...on a fresh install that seems odd but it's a different issue.
Ok, this worked for me too after i migrated the db (missed that part). Not sure why nginx config suddenly breaks after latest, but anyhow, this should probably be added to the README. :+1:
As mentioned by @718aba I find adding the Host header helps, though I found adding the port on the container didn't, so:
proxy_set_header Host $host;
Thank you for your input; Unfortunately this recommendation does not work for me. I am already using the root "/" of my web server and with this option everything is redirected there after login. Example: Now the call is done via https://domain:port after the login I always end up on https://domain/login but it should be https://domain:port/login.
Found it; in this case the server port can also define:
proxy_set_header Host $host:$server_port;
2.6.6 runs here now too. Thanks!
I met the same problem behind apache reverse proxy.
Solved with ProxyPreserveHost On
.
I have an active wallabag 2.5.2 setup and facing some rewrite problems after upgrade to 2.5.4. Here is my composer setup (without certificate) to recreate; just make sure you create the instance with 2.5.2.
docker-compose.yml
demo nginx.conf according to your notes:
start it up: 4Bob@NUC-Desk:~/Apps/wallabag$ docker-compose up
Upgrade so far looks good, but my SYMFONYENVDOMAIN_NAME http://nuc-desk/ is now being rewritten to https://wallabag
Can you please help me further?