ssinseeme

I just installed Hassio supervisor and ran with no other editing. I don'tt see the new HASSIO tab in home assistant core? an other question home do i set up HA with reverse proxy to access from outside.

Hi I posted this already but in a wrong thread. I have issues connecting to bitwarden using my domain. I used to use duckdns for domain and it didn't work so I decided to have my own domain to try and see if bitwarden would work. first, I know that Letenrypt is set up right with my domain name and subdomains, the log connected to all my 2 subdomain Nextcloud, bitwarden. I . made sure the Cnam is set right spelled right... Second, my duckdns is set up right since my Nextcloud is working following Spaceenvador's Video for Bitwarden, i set up the network to custom, just like Nextcloud. I tried 2 different config files in letencryp for bitwarden, one with spaceinvador file and i left the container name as original with bitwardenrs of course i alway restart my dockers. #BITWARDEN # make sure that your domain has dns has a cname or a record set for the subdomain bitwarden # This config file will work as is when using a custom docker network the same as letesencrypt (proxynet). # However the container name is expected to be "bitwardenrs" as it is by default the template as this name is used to resolve. # If you are not using the custom docker network for this container then change the line "server bitwardenrs:80;" to "server [YOUR_SERVER_IP]:8086;" Also remove line 7 resolver 127.0.0.11 valid=30s; upstream bitwarden { server bitwardenrs:80; } server { listen 443 ssl; server_name bitwarden.*; include /config/nginx/ssl.conf; client_max_body_size 128M; location / { proxy_pass http://bitwarden; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; } location /notifications/hub { proxy_pass http://bitwarden; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } location /notifications/hub/negotiate { proxy_pass http://bitwarden; } } second i tried the default config which what was in letenrypt and change .sample to .conf and i change the container name to bitwarden. make sure that your dns has a cname set for bitwarden and that your bitwarden container is not using a base url # make sure your bitwarden container is named "bitwarden" server { listen 443 ssl; listen [::]:443 ssl; server_name bitwarden.*; include /config/nginx/ssl.conf; client_max_body_size 128M; # enable for ldap auth, fill in ldap details in ldap.conf #include /config/nginx/ldap.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 /login; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app bitwarden; set $upstream_port 80; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } location /notifications/hub { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app bitwarden; set $upstream_port 80; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "Upgrade"; } location /notifications/hub/negotiate { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app bitwarden; set $upstream_port 80; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } } now the weird part. when i use http://bitwarden.mydomain.com it will direct me to nextcloud i don't understand why?, when i stop nextcloud and try again i have error 502 Bad Gateway nginx/1.16.1 i am able only to connect locally with bitwarden i dont know what am i missing. this was the same using duckdns as domain

something wrong in Nextoud docker or the other docker "bitwaerden"

Also i forget to mention that when i use "bitwarden.mydomain.com" it redirect me to my Nextcould why is that??

i have the same problem with other dockers to access like "bitwarden" it works locally but not with letenrypt. i am trying to find out what to comment out in "appdata\letsencrypt\nginx\site-confs" i don't see what you see could you share the config default.

I am not an expert since I have some issue. But. Did you have port forwarding set up right and the config file in letencrypt ok. Do you have anything else running on reverse proxy running ok. It seem to be Letencrypt issues

Finally! thank you very much man, was very helpful. it was actually sudo -u abc php7 /config/www/nextcloud/occ files:scan --all i hope this will be useful for newbies like me. the mysterious first post! had too many links.

I am sorry but there was not a quote " " and where to click is not hyperlink this is what you wrote " It's there. Click here (in the first post). For upgrading the Nextcloud version, please see this guide here."

This is the first post bellow, I understand that you want me to read and find it by my self, but i am telling you i can't find OCC code to scan and what ever i found didn't work for me. could you just give me the code, or if you want me to find it then at list give me the right link to read. thanks for the replies linuxserver_medium.png Application Name: Nextcloud Application Site: https://nextcloud.com/ Docker Hub: https://hub.docker.com/r/linuxserver/nextcloud/ Github: https://github.com/linuxserver/docker-nextcloud Note: Requires MariaDB or MySQL, please note the issues with binlogging detailed here. This is a Nextcloud issue which we have no control over. For setup guide please see the article on our website here. For upgrading the Nextcloud version, please see this guide here. Alternatively, you can update via the Nextcloud webui. Please post any questions/issues relating to this docker you have in this thread. If you are not using Unraid (and you should be!) then please do not post here, instead head to linuxserver.io to see how to get support.

I could not find "The manual update procedure" in the first post. checked all the links. Could you please share the OCC code. I dont know much about linux stuff. I did some research for how to scan new files in dockers but can't find anything.

this is what i get when write the script in Nextcloud consol: root@f46059fee259:/# sudo -u www-data php occ files:scan sudo: unknown user: www-data sudo: unable to initialize policy plugin

I was able to set up Nextcloud with spaceinvador video. but it seems like Nextcloud is hijacking all other docker Https. what i mean is when I set up my Bitwarden and use my https://bitwarden.mydomain.com it will direct me to nextcloud UI. I can't set up anything else that work with reverse proxy other then Nextcloud. I tried also to follow Spaceinvador for "onlyofficedocumentserver" video and it doen't work. I am trying to figure out where the problem is. this is from a different thread where i have my set up for Bitwarden. I don't where is the issue; I used first dock DNS as my domain, it didn't work so i decided to have my own domain to try and see if bitwarden would work. i will write all the steps and please let me know if i am missing something. first, I know that Letenrypt is set up right with my domain name and subdomains, the log connected to all my subdomains: Nextcloud, bitwarden. see image. made sure the Cnam is set right spelled right... Second, my duckdns is set up right since my Nextcloud is working following Spaceenvador's Video for Bitwarden, yes i set up the network to custom, just like Nextcloud. I tried 2 different config files in letencryp for bitwarden, one with spaceinvador file and i left the container name as original with bitwardenrs of course i alway restart my dockers. #BITWARDEN # make sure that your domain has dns has a cname or a record set for the subdomain bitwarden # This config file will work as is when using a custom docker network the same as letesencrypt (proxynet). # However the container name is expected to be "bitwardenrs" as it is by default the template as this name is used to resolve. # If you are not using the custom docker network for this container then change the line "server bitwardenrs:80;" to "server [YOUR_SERVER_IP]:8086;" Also remove line 7 resolver 127.0.0.11 valid=30s; upstream bitwarden { server bitwardenrs:80; } server { listen 443 ssl; server_name bitwarden.*; include /config/nginx/ssl.conf; client_max_body_size 128M; location / { proxy_pass http://bitwarden; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; } location /notifications/hub { proxy_pass http://bitwarden; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } location /notifications/hub/negotiate { proxy_pass http://bitwarden; } } second i tried the original config in Letinrypt and chnage .sample to .conf and i change the container name to bitwarden. # make sure that your dns has a cname set for bitwarden and that your bitwarden container is not using a base url # make sure your bitwarden container is named "bitwarden" server { listen 443 ssl; listen [::]:443 ssl; server_name bitwarden.*; include /config/nginx/ssl.conf; client_max_body_size 128M; # enable for ldap auth, fill in ldap details in ldap.conf #include /config/nginx/ldap.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 /login; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app bitwarden; set $upstream_port 80; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } location /notifications/hub { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app bitwarden; set $upstream_port 80; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "Upgrade"; } location /notifications/hub/negotiate { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app bitwarden; set $upstream_port 80; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } } now the weird part. when i use http://bitwarden.mydomain.com it will direct me to nextcloud i don't understand why?, when i stop nextcloud and try again i have error 502 Bad Gateway nginx/1.16.1 i am able only to connect locally with bitwarden i dont know what am i missing. this was the same using duckdns as domain

Hi deadnote, first thanks for trying to help me. i decided to have my own domain to try and see if bitwarden would work. i will write all the steps and please let me know if i am missing something. first, I know that Letenrypt is set up right with my domain name and subdomains, the log connected to all my 2 subdomain Nextcloud, bitwarden. see image. made sure the Cnam is set right spelled right... Second, my duckdns is set up right since my Nextcloud is working following Spaceenvador's Video for Bitwarden, yes i set up the network to custom, just like Nextcloud. I tried 2 different config files in letencryp for bitwarden, one with spaceinvador file and i left the container name as original with bitwardenrs of course i alway restart my dockers. #BITWARDEN # make sure that your domain has dns has a cname or a record set for the subdomain bitwarden # This config file will work as is when using a custom docker network the same as letesencrypt (proxynet). # However the container name is expected to be "bitwardenrs" as it is by default the template as this name is used to resolve. # If you are not using the custom docker network for this container then change the line "server bitwardenrs:80;" to "server [YOUR_SERVER_IP]:8086;" Also remove line 7 resolver 127.0.0.11 valid=30s; upstream bitwarden { server bitwardenrs:80; } server { listen 443 ssl; server_name bitwarden.*; include /config/nginx/ssl.conf; client_max_body_size 128M; location / { proxy_pass http://bitwarden; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; } location /notifications/hub { proxy_pass http://bitwarden; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } location /notifications/hub/negotiate { proxy_pass http://bitwarden; } } second i tried you config which is the same as what was in letenrypt and change .sample to .conf and i change the container name to bitwarden. # make sure that your dns has a cname set for bitwarden and that your bitwarden container is not using a base url # make sure your bitwarden container is named "bitwarden" server { listen 443 ssl; listen [::]:443 ssl; server_name bitwarden.*; include /config/nginx/ssl.conf; client_max_body_size 128M; # enable for ldap auth, fill in ldap details in ldap.conf #include /config/nginx/ldap.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 /login; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app bitwarden; set $upstream_port 80; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } location /notifications/hub { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app bitwarden; set $upstream_port 80; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "Upgrade"; } location /notifications/hub/negotiate { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app bitwarden; set $upstream_port 80; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } } now the weird part. when i use http://bitwarden.mydomain.com it will direct me to nextcloud i don't understand why?, when i stop nextcloud and try again i have error 502 Bad Gateway nginx/1.16.1 i am able only to connect locally with bitwarden i dont know what am i missing. this was the same using duckdns as domain

“then run the update files command” i am ready the document https://docs.nextcloud.com/server/15/admin_manual/configuration_server/occ_command.html I don’t know which OCC commande I should use I don’t see anything for database update. If I have the commande should I run in terminal. Or use putty

what is the fastest way to transfer files from my Unraid disk to Nextcould? I recently deleted my Nextcould docker accidentally, i was not sure how to restore the docker using the addon backup, and not sure if it will restore my docker as well as all the files i had in it. It takes for ever to upload large files from window app. since i am using my disk 1, and a share file called Nextcloud to store all my cloud files, why can't i see these files in my Nextcould webUI or IOS App. it works only one way. it will be convenient to use Krusader to transfer file from disk to user/Nextcould folder! second question: how do i fix this: 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 thank you

It there a fast way to transfer files to next cloud. Uploading large file from the web takes forever.

I have my duckDNS running ok. Like I said I followed Space invader Nextcould set and everything works fine. Means duckdns and let encrypt works. Although the weird part is when I use mynamebitwarden.duckdns.org the website get directed to my Nextcloud. I don’t understand why. I set up my next cloud with mynamenextcloud as subdomain. !! i don’t understand what am I missing. i can’t use exactly bitwarden as my subdomain because I am using Duckdns for my subdomain and bitwarden is taken. So I called it mynamebitwarden. i even removed all subdomains from duckdns and letencrypt , stoped Nextcloud and left only mynamebitwarden just to try and still have and have error 502 bad Hathaway Nginx 1.16.1

I followed Spaceinvador’s YouTube video step by step. The only difference I am seeing reading the forum and space invader is that I am using DuckDns to creat my subdomain and I guess everyone else is using their payed domain. duckdns is setup right and running on unraid letencrypt running with no error and the config file is set up with the subdomain. I don’t know what else I am missing.

I opened port 80 and 443 just like he showed in video. Is there another port to open? I tried your config file. Changed the name of the docker as you instructed. It still not working. I have my Nextcloud working, at least it created an Https with duckdns and I can access from out side. Although there is errors in next cloud about rever proxy I don’t know what it means. anyway. Is your bitwarden works fine using your domain.

I believe it something wrong with the bitwarden config file in letencrypt. my nextcloud seem to work ok. if you don't mind sharing what do you use for domain, i may have to pay for a subscription. and if you can please share your Bitwarden config file of course with out your subdomain . thanks for the replies.

#BITWARDEN # make sure that your domain has dns has a cname or a record set for the subdomain bitwarden # This config file will work as is when using a custom docker network the same as letesencrypt (proxynet). # However the container name is expected to be "bitwardenrs" as it is by default the template as this name is used to resolve. # If you are not using the custom docker network for this container then change the line "server bitwardenrs:80;" to "server [YOUR_SERVER_IP]:8086;" Also remove line 7 resolver 127.0.0.11 valid=30s; upstream bitwarden { server bitwardenrs:80; } server { listen 443 ssl; server_name mynamebitwarden.*; include /config/nginx/ssl.conf; client_max_body_size 128M; location / { proxy_pass http://bitwarden; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; } location /notifications/hub { proxy_pass http://bitwarden; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } location /notifications/hub/negotiate { proxy_pass http://bitwarden; } } This is what Spaceinvadore shared, it looks different than your config file. I only changed the subdomain as you see. it is added to duckdns and letencript my bitwarden container name is bitwardens as default. should i just copy and past your configuration? of course i will change the subdomain and will change the container to bitwarden instead.

Oh. Man no reply to this either. I think I have the same issue. Did you resolve this issue.

I still have a problem getting Bitwarden to work with letencrypt. Other then letencrypt config file modification with subdomain. Is there anything else that need to me changed I set up duckdns with a new bitwarden subdomain. added the subdomain to letencrypt and modified the config file. Anything else I am missing.

yes, i have it set up right i have "mynamenextcloud,mynamebitwarden". just like that. I watched the video many times. i updated the config file he shared with mynamebitwarden.* i don't know what else. its working fine locally. i can access the web ui and set password in chrom. something not right with the config file i guess. did you follow the video and it worked? did you change anything in Letencrypt config file other then the subdomain?