You do realize that there install scripts that are available for use where you are not going into each and every config file and altering them. To think otherwise is beyond belief.
If everyone in the “HELP FORUMS” knew what the problem was and how to fix the problem, then there would be no need for the forums. The fact that this has to be verbalized is beyond belief.
If someone is asking for help, I am pretty sure that they are not wanting some troll to come along and bash their statement and give them some crappy response of, “well how did you install this in the first place if you don’t know where a config file is.”
This is exactly the reason why the documentation is rather generic, because it is impossible to include every possible installation type and distribution.
You didn’t ask for help. You were demanding things, and you were complaining about other users who tried to help here voluntarily. Imagine someone does hijack an old thread, just to complain that the posts in it, which were addressed to completely different people, did not help with their own issue… Would you be motivated to help that person?
Anyways… If you’re still interested in getting help, I suggest you open a new thread and provide as much information as you can. The bare minimum would be a link to that installation script you used… Good Luck.
server {
listen 80 default_server;
listen [::]:80 default_server;
listen 443 ssl http2 default_server;
listen [::]:443 ssl http2 default_server;
server_name _;
include /config/nginx/ssl.conf;
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;
Nginx users can follow these instructions to solve this problem:
In summary, it involves adding a line like this to your /etc/nginx/sites-available/my_nc_site config: add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
Like @Witzker , my nextcloud is hosted at Ionos (Germany) which is shared hosting.
nextcloud is installed in a subdirectory …/htdocs/nextcloud. Access is via the subdomain cloud.domainxy.de
For the main domain I can configure HSTS with the .htaccess. That works.
If I remove the .htaccess in subdir. /nextcloud/ HSTS works also for the subdomain cloud.domainxy.de (but in this case not CSP) (tested with observatory.mozilla.org).
With .htaccess in sub directory /nextcloud/, no matter what I add, I cannot get HSTS to work for the subdomain.
Any idea, what breaks the actually working HSTS-Header "Header always set Strict-Transport-Security “max-age=31536000; includeSubDomains; preload” in the top-level htaccess?
Yes.
This is strange
I asked the forum to get a separate group for Nextcloud on webspace but no answer.
I think for us will be good to have a separate group.
How can this be done in this forum.
Yesterday I started a search for IONS to find others with the same problems, what IONOS is concerned - It’s not the only one.
e.g
If you are interested, let me know to find a way how we could huddle together and solve the IONOS problems.
What do you think?
PS: there is a TAG IONOS, but I don’t know how to get this in the post.
When you start a new thread and go to
You are a wizard. Had this transport error for well over a year and tried tons of supposed “fixes”, follow the documentation responses, etc. none of them worked. The key truly was to run “sudo a2enmod headers”