saarg
-
Posts
5,374 -
Joined
-
Last visited
-
Days Won
8
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by saarg
-
-
2 hours ago, TBoneStaek said:
- The reverse proxy header configuration is incorrect, or you are accessing Nextcloud from a trusted proxy. If not, this is a security issue and can allow an attacker to spoof their IP address as visible to the Nextcloud. Further information can be found in the documentation.
- The "X-Frame-Options" HTTP header is not set to "SAMEORIGIN". This is a potential security or privacy risk, as it is recommended to adjust this setting accordingly.
Here's my nextcloud.subdomain.conf
# make sure that your dns has a cname set for nextcloud
# assuming this container is called "letsencrypt", edit your nextcloud container's config
# located at /config/www/nextcloud/config/config.php and add the following lines before the ");":
# 'trusted_proxies' => ['letsencrypt'],
# 'overwrite.cli.url' => 'https://nextcloud.your-domain.com/',
# 'overwritehost' => 'nextcloud.your-domain.com',
# 'overwriteprotocol' => 'https',
#
# Also don't forget to add your domain name to the trusted domains array. It should look somewhat like this:
# array (
# 0 => '192.168.0.1:444', # This line may look different on your setup, don't modify it.
# 1 => 'nextcloud.your-domain.com',
# ),
server {
listen 443 ssl;
listen [::]:443 ssl;
server_name nextcloud.*;
include /config/nginx/ssl.conf;
add_header X-Frame-Options "SAMEORIGIN" always;
add_header Strict-Transport-Security "max-age=15768000; includeSubDomains; preload;";
client_max_body_size 0;
location / {
include /config/nginx/proxy.conf;
resolver 127.0.0.11 valid=30s;
set $upstream_nextcloud nextcloud;
proxy_max_temp_file_size 2048m;
proxy_pass https://$upstream_nextcloud:443;
}
}
I've also tried uncommenting out the X-Frames-Options issue in the ssl.conf to no avail.
I just don't see what I'm missing.
You need to check the swag logs and update the config files it mentions.
-
3 hours ago, Aspect said:
understood I guess Ill update when I figure out what it is in case someone else is having a similar issue.
Do you use the IP to connect to nextcloud or reverse proxy limited to Lan only?
-
2 hours ago, Greygoose said:
I am trying to set my maxmind key in the docker by adding a variable.
Its not working
I would be most grateful for some advice.
Config Type: Variable
Name: Maxmind
Key: my Maxmind key
Value: MAXMINDDB_LICENSE_KEY=
Default value: -e
What wrong with the above please.
Everything.
You have switched value and key and also remove =. Default value is also not -e. Just leave it blank.
-
1
-
-
9 hours ago, Aspect said:
@saarg Unfortunately fresh install is having same issue (screen shots of new install)
ill do my best this time to provide the information you need to assist.
I have no idea what is wrong in your setup, but it is something local to you as it works here on a fresh setup and my existing install.
-
13 hours ago, Aspect said:
I don't see the docker run command there and it's not really enough detailed info about what you have done.
But could you try to set up a new nextcloud container and be sure to use anothe folder for both appdata and data. You can use sqlite for database. I just want to see if you get the same errors then, as I'm not getting it.
-
5 hours ago, DockX said:
Hi,
thanks for testing it @saarg. I guess it has something to do with SWAG then. Here is my compose file:
version: "3.3" services: swag: container_name: SWAG image: linuxserver/swag cap_add: - NET_ADMIN ports: - 80:80 - 443:443 volumes: - /data/SWAG:/config - /data/Nextcloud_config/log/nextcloud:/config/log/nextcloud restart: unless-stopped environment: - PUID=1000 - PGID=100 - EMAIL=* - URL=* - SUBDOMAINS=* - ONLY_SUBDOMAINS=true - DHLEVEL=4096 - TZ=Europe/Berlin nextcloud: image: linuxserver/nextcloud container_name: nextcloud hostname: Nextcloud environment: - PUID=1000 - PGID=100 - TZ=Europe/Berlin ports: - 8011:443 volumes: - /data/Nextcloud_config:/config - /data/Nextcloud_data:/data depends_on: - mariadb - redis restart: unless-stopped mariadb: image: linuxserver/mariadb container_name: mariadb environment: - PUID=1000 - PGID=100 - MYSQL_ROOT_PASSWORD=* - TZ=Europe/Berlin volumes: - /data/MariaDB:/configMaybe subfolder.conf needs a change:
## Version 2020/12/09 # Assuming this container is called "swag", edit your nextcloud container's config # located at /config/www/nextcloud/config/config.php and add the following lines before the ");": # 'trusted_proxies' => ['swag'], # 'overwritewebroot' => '/nextcloud', # 'overwrite.cli.url' => 'https://your-domain.com/nextcloud', # # Also don't forget to add your domain name to the trusted domains array. It should look somewhat like this: # array ( # 0 => '192.168.0.1:444', # This line may look different on your setup, don't modify it. # 1 => 'your-domain.com', # ), # Redirects for DAV clients location = /.well-known/carddav { return 301 $scheme://$host/nextcloud/remote.php/dav; } location = /.well-known/caldav { return 301 $scheme://$host/nextcloud/remote.php/dav; } location /nextcloud { return 301 $scheme://$host/nextcloud/; } location ^~ /nextcloud/ { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app nextcloud; set $upstream_port 443; set $upstream_proto https; proxy_pass $upstream_proto://$upstream_app:$upstream_port; rewrite /nextcloud(.*) $1 break; proxy_max_temp_file_size 2048m; proxy_set_header Range $http_range; proxy_set_header If-Range $http_if_range; proxy_redirect off; proxy_ssl_session_reuse off; }I'm confused now. Are you having two accounts here and posting as aspect also or did you just piggytail on his problem answering my post to him.
Seeing you are not using unraid, please go to linuxserver.io/support and either join our discord or discourse forum to get support. This is for unraid users only.
-
7 hours ago, DockX said:
I have tried incognito and other devices. But the message stays.
I just installed a fresh nextcloud container here and there are no messages about missing well-known stuff.
Post your docker run command, how you connect to nextcloud and exactly what you have been doing to try to fix it. And use the code tag.
-
13 hours ago, Aspect said:
upstream php-handler {
server 127.0.0.1:9000;
}
server {
listen 80;
listen [::]:80;
server_name _;
return 301 https://$host$request_uri;
}
server {
listen 443 ssl http2;
listen [::]:443 ssl http2;
server_name _;
ssl_certificate /config/keys/cert.crt;
ssl_certificate_key /config/keys/cert.key;# Add headers to serve security related headers
# Before enabling Strict-Transport-Security headers please read into this
# topic first.
add_header Strict-Transport-Security "max-age=15768000; includeSubDomains; preload;" always;
#
# WARNING: Only add the preload option once you read about
# the consequences in https://hstspreload.org/. This option
# will add the domain to a hardcoded list that is shipped
# in all major browsers and getting removed from this list
# could take several months.# set max upload size
client_max_body_size 512M;
fastcgi_buffers 64 4K;# Enable gzip but do not remove ETag headers
gzip on;
gzip_vary on;
gzip_comp_level 4;
gzip_min_length 256;
gzip_proxied expired no-cache no-store private no_last_modified no_etag auth;
gzip_types application/atom+xml application/javascript application/json application/ld+json application/manifest+json application/rss+xml application/vnd.geo+json application/vnd.ms-fontobject application/x-font-ttf application/x-web-app-manifest+json application/xhtml+xml application/xml font/opentype image/bmp image/svg+xml image/x-icon text/cache-manifest text/css text/plain text/vcard text/vnd.rim.location.xloc text/vtt text/x-component text/x-cross-domain-policy;# HTTP response headers borrowed from Nextcloud `.htaccess`
add_header Referrer-Policy "no-referrer" always;
add_header X-Content-Type-Options "nosniff" always;
add_header X-Download-Options "noopen" always;
add_header X-Frame-Options "SAMEORIGIN" always;
add_header X-Permitted-Cross-Domain-Policies "none" always;
add_header X-Robots-Tag "none" always;
add_header X-XSS-Protection "1; mode=block" always;# Remove X-Powered-By, which is an information leak
fastcgi_hide_header X-Powered-By;root /config/www/nextcloud/;
# display real ip in nginx logs when connected through reverse proxy via docker network
set_real_ip_from 172.0.0.0/8;
real_ip_header X-Forwarded-For;# Specify how to handle directories -- specifying `/index.php$request_uri`
# here as the fallback means that Nginx always exhibits the desired behaviour
# when a client requests a path that corresponds to a directory that exists
# on the server. In particular, if that directory contains an index.php file,
# that file is correctly served; if it doesn't, then the request is passed to
# the front-end controller. This consistent behaviour means that we don't need
# to specify custom rules for certain paths (e.g. images and other assets,
# `/updater`, `/ocm-provider`, `/ocs-provider`), and thus
# `try_files $uri $uri/ /index.php$request_uri`
# always provides the desired behaviour.
index index.php index.html /index.php$request_uri;# Rule borrowed from `.htaccess` to handle Microsoft DAV clients
location = / {
if ( $http_user_agent ~ ^DavClnt ) {
return 302 /remote.php/webdav/$is_args$args;
}
}
# Make a regex exception for `/.well-known` so that clients can still
# access it despite the existence of the regex rule
# `location ~ /(\.|autotest|...)` which would otherwise handle requests
# for `/.well-known`.
location ^~ /.well-known {
# The following 6 rules are borrowed from `.htaccess`location = /.well-known/carddav { return 301 /remote.php/dav/; }
location = /.well-known/caldav { return 301 /remote.php/dav/; }
# Anything else is dynamically handled by Nextcloud
location ^~ /.well-known { return 301 /index.php$uri; }try_files $uri $uri/ =404;
}# Rules borrowed from `.htaccess` to hide certain paths from clients
location ~ ^/(?:build|tests|config|lib|3rdparty|templates|data)(?:$|/) { return 404; }
location ~ ^/(?:\.|autotest|occ|issue|indie|db_|console) { return 404; }# Ensure this block, which passes PHP files to the PHP process, is above the blocks
# which handle static assets (as seen below). If this block is not declared first,
# then Nginx will encounter an infinite rewriting loop when it prepends `/index.php`
# to the URI, resulting in a HTTP 500 error response.
location ~ \.php(?:$|/) {
fastcgi_split_path_info ^(.+?\.php)(/.*)$;
set $path_info $fastcgi_path_info;try_files $fastcgi_script_name =404;
include /etc/nginx/fastcgi_params;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
fastcgi_param PATH_INFO $path_info;
fastcgi_param HTTPS on;fastcgi_param modHeadersAvailable true; # Avoid sending the security headers twice
fastcgi_param front_controller_active true; # Enable pretty urls
fastcgi_pass php-handler;fastcgi_intercept_errors on;
fastcgi_request_buffering off;
}location ~ \.(?:css|js|svg|gif)$ {
try_files $uri /index.php$request_uri;
expires 6M; # Cache-Control policy borrowed from `.htaccess`
access_log off; # Optional: Don't log access to assets
}location ~ \.woff2?$ {
try_files $uri /index.php$request_uri;
expires 7d; # Cache-Control policy borrowed from `.htaccess`
access_log off; # Optional: Don't log access to assets
}location / {
try_files $uri $uri/ /index.php$request_uri;
}}
Next time you post a config file or log, please use the code formatting. It's not easy to look at this on a mobile device when the formatting is screwed up.
The file looks like it's the latest version, so try using incognito mode or private mode in your browser.
-
5 hours ago, b0m541 said:
Same crap here, just updated.. sad.
Press OK, and then you should get the login window. You might have to remove the previous set env variable for user/password as the base image was changed. It's in the changelog of the readme.
-
3 hours ago, skois said:
Wait, I have the impression, that well known error fix needs the server accessible through reverse proxy. But I'm not really sure.
Sent from my Mi 10 Pro using Tapatalk
The fix is in the default file of the nextcloud container.
-
4 hours ago, Aspect said:
Hello everyone. especially @skois and @saarg as it seems like you answer this question the most. and i have read multiple times where you reference the fix to this issue but i am still having the "well-known/" issues (pasted below). I have tried all fixes on this forum and on the github issues such as deleting default file, clearing browser cache (even tried the way mentioned on git issue by right clicking the refresh and doing the dump and hard reload that way.), Ive changed the docker tags, updated nextcloud to latest version 21.0.1. I'm not using any proxy nextcloud is only available on my local network or through VPN. unraid version 6.9.2 (if this matters in this situation)
I can provide any logs, outputs, or info needed.
i really am sorry if i passed over the answer to this question but last night i read through the last 92 pages post by post and have not found a solution to my issue.
The last option i haven't tried is complete delete the docker and try again but from everything i read that's not the solution and ill still have same issue.
Your web server is not properly set up to resolve "/.well-known/webfinger". Further information can be found in the documentation.
Your web server is not properly set up to resolve "/.well-known/nodeinfo". Further information can be found in the documentation.
Your web server is not properly set up to resolve "/.well-known/caldav". Further information can be found in the documentation.
Your web server is not properly set up to resolve "/.well-known/carddav". Further information can be found in the documentation.
Post your default file.
-
10 hours ago, Carlos said:
Hi there,
As as said before, my smartphone won't connect to the Nextcloud server using the domain via WiFi neither using the browser nor the app (using 4G works fine). For a moment Pi-Hole crossed my mind as a possible cause but disabling it nothing changes.
Cheers
Then it's something in your network not resolving the domain.
-
1
-
-
2 hours ago, Carlos said:
It was working fine till latest Nextcloud update
PS: my PC access the Nextcloud server (in the same LAN) using the domain (via browser and desktop app) without problems
Still nothing with the container itself. Then it's either nextcloud, your phone, the nextcloud client or your router.
Did you try using the browser on your phone? If it works using your domain there it's either the client or nextcloud itself.
-
1 hour ago, TBoneStaek said:
I'm having the same issue after pulling the latest image. It's like it "forgot" where my library is and every time I repoint to it and restart the docker it "forgets" again. I'm getting errors in my logs as well.
https://privatebin.net/?6cb378d34ade868b#Euikg6Kvz2K4XK1xJq7V1U6a7Mz65Vz47f9wdraoAPUV
It's getting fixed.
-
1
-
-
15 hours ago, plantsandbinary said:
I just realised these guys haven't been here since Feb 23rd. So I think I am going to give all their containers a miss for now...
When have you seen us post anything support related with that account? It's only used to start the support thread, which we now stopped doing and will not do anymore as we want support to happen on our platforms.
There are nobody else reporting any chrashes using our container, so it's a local issue. The container is receiving a signal to stop, so you will have to figure out what does that.
-
9 hours ago, Carlos said:
I've been fiddling with this mess all afternoon and I'm still at square one... I even nuked Nextcloud+MariaDB and started over but the result is the same. My Android phone connects fine via 4G (cellular data) but there's no way to make it work via WiFi with the reverse proxy active (swag) nor app nor android browser. However, if Nextcloud is set without reverse proxy (access via 192.168.x.x) my Android phone can connect fine... I'm starting to think there's some problem between swag and this Nextcloud update.
PS: the media visualization problem was fixed ditching SMB/CIFS external storage and mappig the shares as local
This has nothing to do with the container setup. It's your router that doesn't support NAT hairpin/split DNS out of the box.
-
6 hours ago, SaltShakerOW said:
I just setup a NGINXProxyManager w/ Cloudflare and I got everything to work outside of Nextcloud where it gives me an error upon going to the url that says:
Since all of my other containers work file with the setup I have going, I am posting here to figure out why my nextcloud docker isn't cooperating with me on this. If anyone has had this problem and found a solution, please shoot me a response. Thanks in advance.
You have to use https from your proxy to nextcloud.
-
16 hours ago, Der_Eine said:
Hey,
today I have updated nextcloud since a long time. When I try to access the webui I get this error notification:
This version of Nextcloud is not compatible with > PHP 7.3.
You are currently running 7.4.15.Anyone know what to do?
Yes, read the previous posts.
-
1
-
-
10 hours ago, Monty said:
I'm having a weird issue with setting a user and pass in the docker config page.
Latest version of linuxserver/calibre - the environmental variables for GUAC_USER & GUAC_PASS do not work - still have to log in with abc / abc.
Cannot figure out how to change this (an I'm pretty sure I'm being silly)
6 hours ago, dcpdad said:@Monty I can confirm that I am having the same issue. This started for me after yesterday's Docker update.
Might be worth it to read the documentation some times 😉
-
9 hours ago, tcm2Lions said:
Not sure if the is the correct place to ask but my UNRAID Nextcloud is suddenly broken and will not connect. I get this error "This version of Nextcloud is not compatible with > PHP 7.3.
You are currently running 7.4.15." Nextcloud is a good app and would hate to have to remove it. Anyone have any answers to this problem?There might be a couple of hundred post about the same issue in this thread, so a search would be welcome 😉
In short, you haven't updated nextcloud in a long time.
-
1 hour ago, goalcam said:
I'm somewhat confused about why FoxxMD's pinry application is seemingly 'stuck' to the Trending and Top New Installs for at least the past few weeks if not longer. I don't mean to disparage their hard work on their project, but I'm having a hard time believing that a selfhosted version of pinterest is setting the world on fire, especially given that the Unraid support thread has a whopping 10 posts, none in the last six months.
So that's why squid is driving around in a fancy new sports car 😆
-
14 hours ago, DingHo said:
Does that mean the existing container will stay on the final release of forked-daap and cease to be updated or it will just keep the existing name and still get updated from the new project?
Thanks, and I appreciate your efforts.
It's building from the new repo.
-
18 hours ago, Alex.b said:
Hello I have an error with a serie who try to detect intro, this erros keeps disks spin up for days :
Do you have an idea why ? Thank you !
As usual with Plex codecs errors, deleting the Codecs folder and restarting Plex usually fixes the problem.
-
3 hours ago, S80_UK said:
Personally, I don't care what it's called, so long as I don't lose the functionality that I happen to use. For me, that's streaming to Roku SoundBridge clients. I've been using daapd in one form or another since 2006 when it was still called Firefly Media Server. 🙂
We have discussed it internally now, and we will not release a new container under the new name. Daapd is now maintained by a community member (our community, not unraid).
-
1
-
I would be most grateful for some advice.
[Support] Linuxserver.io - Booksonic-air
in Docker Containers
Posted
Have you tried using a previous tag?
There are only dependencies updated in the latest build 2 days ago.