Closed Nidwan closed 2 years ago
Reading the Nginx error.log, is it possible the issue is related to the nginx config file from Swag ? I know only little about Nginx but I can see there's an "undefined variable" [...] "while reading response header from upstream". It made me think about my nginx site-proxy conf file, which has this line (I've copied the whole file below) :
proxy_set_header X-Forwarded-Port $server_port;
I'm not sure if it's relevant or not, but I tried to echo this variable from the container itself. It didn't returned anything:
docker exec -ti freshrss bash
echo $server_port
Here's my complete freshrss.subdomain.conf file. The only three things, I edited from the sample are :
## Version 2020/12/09
# make sure that your dns has a cname set for freshrss
server {
listen 443 ssl;
listen [::]:443 ssl;
server_name freshrss.*;
# ask Google not to index
add_header X-Robots-Tag "noindex, nofollow, nosnippet, noarchive";
include /config/nginx/ssl.conf;
client_max_body_size 0;
# enable for ldap auth, fill in ldap details in ldap.conf
#include /config/nginx/ldap.conf;
# enable for Authelia
#include /config/nginx/authelia-server.conf;
location / {
# enable the next two lines for http auth
#auth_basic "Restricted";
#auth_basic_user_file /config/nginx/.htpasswd;
# enable the next two lines for ldap auth
#auth_request /auth;
#error_page 401 =200 /ldaplogin;
# enable for Authelia
#include /config/nginx/authelia-location.conf;
include /config/nginx/proxy.conf;
resolver 127.0.0.11 valid=30s;
set $upstream_app 192.168.1.2;
set $upstream_port 85;
set $upstream_proto http;
proxy_pass $upstream_proto://$upstream_app:$upstream_port;
proxy_redirect off;
proxy_buffering off;
proxy_set_header X-Forwarded-Port $server_port;
proxy_cookie_path / "/; HTTPOnly; Secure";
proxy_set_header Authorization $http_authorization;
proxy_pass_header Authorization;
}
}
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Expected Behavior
To be able to add a feed, without an error message.
Current Behavior
Error message displayed : "The newsfeed could not be added. Check FreshRSS logs for details. You can try force adding by appending #force_feed to the URL."
Steps to Reproduce
Environment
OS: Debian 9.13 / OpenMediaVault 4.1.36 CPU architecture: x86_64 How docker service was installed: NAS OS provided (OpenMediaVault 4)
Command used to create docker container (screenshot)
Docker logs
Log from the FreshRSS WebUI
PHP log
Nginx access.log
Nginx error.log
Docker container log