Posts by HannesJo

What site is that. I cannot even play your vid. Best you can do now is do nothing but what you are being told here.

What do you mean by Heimdall connecting to ips? In the end of the day it’s always your browser that connects. If it connects directly or via pihole or via swag or via both depends on your links and your configuration. Everything is possible

Depends

I see. Just be careful with it’s information. The dashboard seems buggy to me. It counts 10 banned ip addresses only, while in fact it is sth like 600

Quote from k4ZzTBG7Gk

Swag parses these container's logs with its own f2b via the swag dashboard mod

You don’t need the mod. Swag comes with fail2ban out of the box. That being said, you probably don’t need the OMV fail2ban plugin. But I wonder what you think you would win by disabling it. I also have a j5005 and fail2ban produces almost no load at all.

I keep mine activated. It still protects if someone gets into my LAN. But if that happens I‘m propably fucked anyway.

Quote from oopenmediavault

Even though this could be a problem, it is unlikely. I also run nextcloud etc. with swag and I also had those messages, but it still worked without any problem.

I also did not have any issue here but it highly depends on what exact files are listed, what config version is used vs what is current and also what customizations were made.

The fact that you once had these message and still everything worked well does not allow any conclusions to be drawn as to what is likely.

The date of nextcloud conf is correct (https://github.com/linuxserver…oud.subdomain.conf.sample).

The log gives you information about outdated conf files on startup:

**** The following active confs have different version dates than the samples that are shipped. ****
**** This may be due to user customization or an update to the samples. ****
**** You should compare the following files to the samples in the same folder and update them. ****
**** Use the link at the top of the file to view the changelog. ****
/config/nginx/ldap-server.conf
/config/nginx/nginx.conf
/config/nginx/authelia-server.conf
/config/nginx/proxy-confs/plex.subdomain.conf
/config/nginx/proxy-confs/nzbget.subfolder.conf
/config/nginx/proxy-confs/navidrome.subdomain.conf
/config/nginx/proxy.conf
/config/nginx/site-confs/default.conf
/config/nginx/authelia-location.conf
/config/nginx/ssl.conf

These are the files you have to update manually or delete, restart container and redo your customizations accordingly.

Good point. There are still potential pitfalls

If you are familiar with btrfs I don’t see any disadvantage

There is no magic fix. Doing live backups of ext3/4 omv has always the risk of broken consistency. Some say it is very unlikely to really cause problems, but it is the main reason why I use btrfs for system disk.

The idea of page cache is to use free ram space for caching as long as it is not needed elsewhere. That is why your mem usage is considered 14% while still being full of page cache. Everything fine. It is a feature. 😉

It wasn’t my intention to recommend it to you. I also think the external storage app is the way to go.

Anyway I’m not home the next 2 weeks. So can’t help you with this now

Hmm that is what I did and it worked. In general the error means the header is either missing or present multiple times.

I think sharing a productive config publicly can be a potential security risk. You can contact the devs via Matrix or Discord. They provide really good support.

Quote from macom

Mapping a smb share to /data does not work due to incompatible permissions. Has been tried before. You can search the forum.

That is wrong. It perfectly works that way with multi user and even group folder environment. In the beginning I used ACLs but lately disabled ACL completely (to make it less complicated) and now using Samba force user and force group settings to match Nextclouds user and group. On filesystem level access is still restricted to corresponding users by permissions of respective parent directory. Not saying it was easy, but nice project for getting familiar with linux permissions and definitely possible.

Quote from siteswap423

@HannesJo, thank you for the reply, i found the problem .

I have removed the "#" in the swag's ssl.conf , at the "X-Robots-Tag line ( my mistake ).

Now is ok,

Br

Daniele.

Nice 👍 … If swag is the only way your Nextcloud is accessible and you also access other apps via swag, you may re-activate it here and disable at Nextcloud to prevent the error. You should find it at Nextcloud‘s /config/nginx/site-confs/default.

Quote from siteswap423

Hi, same error message about :

"

The "X-Robots-Tag" HTTP header is not set to "none". This is a potential security or privacy risk, as it is recommended to adjust this setting accordingly."

How did you solve that ??

Br

Daniele.

Display More

The problem was that he added a custom header for X-Robots-Tag in the file nextcloud.subdomain.conf. This header is already set at another place what caused the error. In general when you really stick to the guide you don’t get the error.

That’s what happens to a lot of boomers these days, sadly

Quote from KM0201

I didn't think identifying by gender was appropriate anymore? Now we just identify as persons...lol. (clown world, I tell you)

In the other hand just now you the only person who bothered me this week with that annoying topic (no offense). Just let them talk how they want and do it your own way. I also don’t understand a single word of Bavarian slang. Still having no problem with it. Language is kind of living. It is how it is. No one should try to dictate anything, doesn’t matter if pro or con gender