Alles anzeigenHi, 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.
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 
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
This is not criticism. When you criticize you DON'T offer a solution.
Bullshit. Of course it is. And makes no difference anyway.
Edit: But would be interesting to know why you think offered solution makes a statement no criticism. Never heard of that.
Most likely everybody else that is new like me is doing the same.
It is a typical mistake to conclude from oneself to everybody. When I started with OMV, I also had never seen anything like it and still never had any problems with it. The many confirmations with OMV6 also bothered me. But here votdev has already relented and scaled it back.
When I started I was having a hard time to get the difference between sharedfolder privileges and filesystem permissions / acl. Still I would not say it is a problem everyone has. However, votdev has recognized this potential lack of information for many users and added a info box to tell them. Despite being against explaining things outside of docs initially. You certainly can't accuse him of not accepting criticism, even if he's against something at first. I assume if enough users have problems with disabled Netbios, he will come up with something. Currently, support requests doesn't seem to indicate it.
The rest of your criticism, e.g. of the dashboard widgets, is personal preference. You don't like the current implementation. I don't get it but thats ok. You can decide for yourself if it is so bad for you that you would rather use another operating system.
Just out of curiosity, are there any cons on enabling netbios? I think tikha has a point that currently it can be pretty difficult to figure out it has to be enabled and how to do it, especially for noobs. Don’t you often say you want things to work out of the box as possible for them?
Not absolutely certain but I think it would not work since your new Nextcloud setup has a new instance id. So you can indeed setup a new Nextcloud instance but I think the client apps will need a re-login and act like it is another Nextcloud instance (what it is).
You can of course try to copy the database files, config.php and data directory from the old Nextcloud instance to the new one. But it is kind of tinkering around and you should backup the files on clients first.
Not absolutely sure atm but yes I think when you search for mce in syslog you should find info about critical hardware errors.
If you use flashmemory plugin it may be necessary to disable it. (It moves logs to ram and so they get lost on a crash. After reboot you can only find logs from before last normal shutdown)
Lot of things can cause that. Anything in the logs? Syslog or journal may be of help. Eventually sth like mce what are typ. hardware errors. However, when I had problems with system crashs it always in the end turned out as RAM problem. Thus out of practical experience I personally would recommend to buy a new ram kit and see if the problem is gone.
Can you also post your docker compose code, your swag proxy-confs/*.nextcloud.conf and proxy.conf? Is your swag a fresh setup or an older one? I think the problem is in the swag proxy conf. Maybe some outdated files or so.
Please stop with the useless comments and just answer my original question!!!!!
You asked for instructions on a repair attempt without risking further damage. That is not possible. How to do it with minimum risk of damage is the way I just described. A new drive is necessary for that. When you cannot effort it, you should put it aside and wait until you can. No offense, no insult, no attitude. Simple facts.
Next time you may give some more information, like what docker image do you actually use, what guide did you use to setup. Not all users here have a magic glass ball.
Seems like nginx/Apache is not configured properly. How did you setup Nextcloud? Used any tutorial? Docker? Non-docker?
I know it is a unfortunate situation, but what you say makes no sense at all. Every try to read from the drive results in I/o errors but you know it is not dead, because it was working fine before and makes no clicking noises? Bro, every drive was working fine before it died. Clicking noises may be an indicator the same way as bad SMART values are.
What you can do is use dd with -noerror flag to force clone the whole drive to a new one while ignoring read errors. That is because every touching of the bad drive may result in even more data damage. You can now try to repair the broken filesystem and read data from the new drive without any risk.
Green SMART is no guarantee that your drive is ok. There are lots of problems SMART doesn’t cover. Your drive has obviously died.
I would simply replace it and recover data from latest backup.
Also you should really consider OMV6. OMV3 is outdated since a very long time.
Where exactly do you have problems with it? äöüß work out of the box for me.
Finally after 2 years he can start doing sth 😂
Unfortunately the best way is fresh setup. Take screenshots of your settings so you can restore them easily.
