Wong

Hi could you guys explain to me why my pihole is not blocking any queries? When I go normal browsing, I can still see ads. I followed the instruction video by the SpaceInvaderOne. For you information, I have let's encrypt docker running and it is using port 443. Does this affect the Pi-Hole?

Final message: To anyone who is reading this, the thread has been solve. Please note that whenever saving the config or subdomain.conf file, please make sure it is not save in text file even though the extension is not shown in window. I change the save as file type as all type. In window 10, the icon of the config file should not look like a text file if you done it correctly.

OHHH MYYY GODDDD, it worked. So the problem is because when I saved the nextcloud.subdomain.conf, notepad++ save it as text file. I edited the save type into all type. Then it worked. It feel good to get things working. Thanks you for the awesome unraid community support.

@saarg This is from letsencrypt. You said do it with both container. I use the same command line for nextcloud container as well? Yes, I am trying to run https://protech.my CNAME is nextcloud root@adb850c459a2:/# ping nextcloud PING nextcloud (172.18.0.4): 56 data bytes 64 bytes from 172.18.0.4: seq=0 ttl=64 time=0.055 ms 64 bytes from 172.18.0.4: seq=1 ttl=64 time=0.051 ms 64 bytes from 172.18.0.4: seq=2 ttl=64 time=0.043 ms 64 bytes from 172.18.0.4: seq=3 ttl=64 time=0.036 ms 64 bytes from 172.18.0.4: seq=4 ttl=64 time=0.035 ms 64 bytes from 172.18.0.4: seq=5 ttl=64 time=0.038 ms 64 bytes from 172.18.0.4: seq=6 ttl=64 time=0.033 ms 64 bytes from 172.18.0.4: seq=7 ttl=64 time=0.027 ms 64 bytes from 172.18.0.4: seq=8 ttl=64 time=0.035 ms 64 bytes from 172.18.0.4: seq=9 ttl=64 time=0.036 ms --- nextcloud ping statistics --- 73 packets transmitted, 73 packets received, 0% packet loss round-trip min/avg/max = 0.026/0.040/0.089 ms

What is a run command? Sorry I am still a newbie. Do you mean the setting page of the container as shown below?

Alright, let break it down. I have register my own domain name (protech.my). The video I followed are link below from SpaceinvaderOne. Let's Encrypt's log said server is ready. Lets' Encrypt port is 80 -> 180 and 443 -> 1443. Port forwarding is done on my router as I able to see the Let's Encrypt WebUi. I attached the log for reference. I am sure nextcloud is working as I have manage to access it locally and set up admin account with Mariadb. For the record, my nextcloud container port is 444. I have used cloudflareddns docker by onzu to track my public IP. I have setup a CNAME nextcloud.protech.my where is point to my public IP. I have setup the nextcloud.subdomain.conf and conf.php I asssume is done correctly already I hope. Let me know if I make any mistake. I attached the file below. I restarted the dockers and still stuck at Let's Encypt Web UI. If anything is not clear, please let me know. I have been stuck with in for a month. It would be if anyone could solve this. I dont mind if I can't get reverse proxy working but if there any method to get onlyoffice working, that would work for me. Thanks. Extra information: (to be very sure my nextcloud is working, I port forwarded 443->444 which is my nextcloud container. I am able to access it from outside my home wifi but when I port forward to 443->1443 and back to stuck in Let'sEncrypt Web UI) and /////////////////////////////////{ LETSENCRYPT LOG }//////////////////////////////////// [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. s6-svwait: fatal: supervisor died [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 01-envfile: executing... [cont-init.d] 01-envfile: exited 0. [cont-init.d] 10-adduser: executing... usermod: no changes ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io ------------------------------------- To support the app dev(s) visit: Certbot: https://supporters.eff.org/donate/support-work-on-certbot To support LSIO projects visit: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... using keys found in /config/keys [cont-init.d] 30-keygen: exited 0. [cont-init.d] 50-config: executing... Variables set: PUID=99 PGID=100 TZ=Asia/Singapore URL=protech.my SUBDOMAINS=wildcard EXTRA_DOMAINS= ONLY_SUBDOMAINS=false VALIDATION=dns DNSPLUGIN=cloudflare EMAIL=**************@gmail.com STAGING= SUBDOMAINS entered, processing Wildcard cert for protech.my will be requested E-mail address entered: [email protected] dns validation via cloudflare plugin is selected Certificate exists; parameters unchanged; starting nginx Starting 2019/12/30, GeoIP2 databases require personal license key to download. Please retrieve a free license key from MaxMind, and add a new env variable "MAXMINDDB_LICENSE_KEY", set to your license key. [cont-init.d] 50-config: exited 0. [cont-init.d] 60-renew: executing... The cert does not expire within the next day. Letting the cron script handle the renewal attempts overnight (2:08am). [cont-init.d] 60-renew: exited 0. [cont-init.d] 99-custom-files: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-files: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html) Server ready ////////////////////////////{ 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; client_max_body_size 0; location / { 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; proxy_max_temp_file_size 2048m; } } /////////////////////{config.php}//////////////////////////////////// <?php $CONFIG = array ( 'memcache.local' => '\\OC\\Memcache\\APCu', 'datadirectory' => '/data', 'instanceid' => 'oc5hdxqy44ml', 'passwordsalt' => '***************************', 'secret' => '********************************', 'trusted_domains' => array ( 0 => '192.168.0.16', 1 => 'nextcloud.protech.my', ), 'dbtype' => 'mysql', 'version' => '19.0.1.1', 'overwrite.cli.url' => 'https://nextcloud.protech.my/', 'dbname' => 'nextcloud', 'dbhost' => '192.168.0.16:3306', 'dbport' => '', 'dbtableprefix' => 'oc_', 'mysql.utf8mb4' => true, 'dbuser' => 'nextcloud', 'dbpassword' => '***********', 'installed' => true, 'trusted_proxies' => ['letsencrypt'], 'overwritehost' => 'nextcloud.protech.my', 'overwriteprotocol' => 'https', 'onlyoffice' => array ( 'verify_peer_off' => true ), );

Hi, so for the reason I can't use http is there is an error in my Letsenrypt log (same error as shown in the 1st version of SpaceInvander Reverse Proxy video). I think my ISP blocked port 80. Thats why I proceed with dns verification. ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container However, there was no error in my log after using dns verification. And stated server ready at the end. Yes I port forward port 80 to 180, 443 to 1443 with TCP/UDP. Just a note, if I only port forward with TCP only of 80 to 180 to my unraid server. I was kick out of my unraid server interface for some reason. But TCP/UDP works for me regardless if is need TCP only. Yes, it is still stuck in the Letencrypt WebUI after setting up Letsencrypt docker again. Let say I dont want to use Reverse Proxy anymore to redirect me to my docker container, do I have another option to try with step by step guide? Cause my purpose is really to get onlyoffice working with nextcloud, can I get onlyoffice to work with or without reverse proxy? (I am replying to my previous thread for anyone that want to refer to my conf file, I have tested all but always still stuck in letsencrypt WebUI)

Ohh my bad. I am sorry.

Hi, so for the reason I can't use http is there is an error in my Letsenrypt log (same error as shown in the 1st version of SpaceInvander Reverse Proxy video). I think my ISP blocked port 80. Thats why I proceed with dns verification. ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container However, there was no error in my log after using dns verification. And stated server ready at the end. Yes I port forward port 80 to 180, 443 to 1443 with TCP/UDP. Just a note, if I only port forward with TCP only of 80 to 180 to my unraid server. I was kick out of my unraid server interface for some reason. But TCP/UDP works for me regardless if is need TCP only. Yes, it is still stuck in the Letencrypt WebUI after setting up Letsencrypt docker again. So I can conclude that my ISP blocked port 80. It is still possible to work with Letencrypt without port 80? Let say I dont want to use Reverse Proxy anymore to redirect me to my docker container, do I have another option to try with step by step guide? Cause my purpose is really to get onlyoffice working with nextcloud, can I get onlyoffice to work without reverse proxy?

I am still a newbie. I read through this whole forum I am having hard time understand the procedure to setup. It would be very helpful to me if anyone could point me where to get the step by step guide link. Firstly, how do I get into the Web UI of this nextcloud docker? There isn't any IP I could access locally.

Is it possible to setup OnlyOffice without using Reverse Proxy? Currently, I am getting Bad Health Check Status. I have setup up a CNAME onlyoffice.protech.my My domain name is protech.my. I have left a screenshot below that I am having trouble with.

@Energen So the changes that I have done is by using CloudflareDDNS docker by oznu and connect to my cloudflare account. I key in the domain section protech.my and leave the subdomain empty. Then, my cloudflare account manage to track it my IP with the domain name protech.my with A record. So I added a CNAME "nextcloud" point to protech.my as shown in the screenshot below. I am still stuck at the nginx Web UI. I know my nextcloud docker is working properly. What version of nextcloud r u guys running? If my nextcloud docker is 192.168.0.16:444. Do I need to adjust anything in subdomain.conf file? Do I need to change the listen 443 ssl to 444 ssl? server { listen 443 ssl; (need to change?) listen [::]:443 ssl; (need to change?) server_name nextcloud.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app nextcloud; set $upstream_port 443; (need to change? I tried 444 but still not directing me to nextcloud) set $upstream_proto https; proxy_pass $upstream_proto://$upstream_app:$upstream_port; proxy_max_temp_file_size 2048m; } }

Alright thank for the suggestion, I think I get what you trying to say. I will try it and let you know in a few days. Cause I think I reach a limit of certificate from Let's Encrypt from here https://letsencrypt.org/docs/rate-limits/. i pasted the log below for reference. Plus, I also let the CNAME propagate for awhile before I test again to makesure it work. I will update the forum again in a week time. Thanks again for been so helpful. An unexpected error occurred: There were too many requests of a given type :: Error creating new order :: too many certificates already issued for exact set of domains: *.protech.my,protech.my: see https://letsencrypt.org/docs/rate-limits/

So if I port forward 443 -> 444 (NextCloud Container Port). I am able to access the nextcloud login page. But then it kinda defeated the purpose of reverse proxy right. So that mean my NextCloud is working properly. Only thing is Let's Encrypt would not pass it to my NextCloud Container for some reason when using my subdomain name. What could be the problem ?😂. I am running out of idea. Yeah it make sense theoretically, but then it is still not directing me to NextCloud.

Yeah tried that. Still remain at the Let's Encrypt UI. Could it be I am running on the beta version 25 of Unraid that is causing the problem. Actually, I don't see any thing in the configuration file that is directing to the NextCloud container. Let say if I use port 444 for nextcloud. Do I need to port forward 444 as well? Edit: Port Forward 444 did not work as well.

@Energen I removed the port and still not working. I attached my nextcloud and letsencrpyt docker configuration screenshot below for reference. It there any problem with my configuration?

Hi guys, I require some help. I can't get let's encrypt docker to redirect to my NextCloud container as shown in the screenshot as it is stuck in the Let's Encrypt Web UI. I have posted my nextcloud.subdomain.conf and config.php file below for reference. I can't spot the mistake. Let me know if I am doing anything wrong. <?php $CONFIG = array ( 'memcache.local' => '\\OC\\Memcache\\APCu', 'datadirectory' => '/data', 'instanceid' => '**********************', 'passwordsalt' => '************************', 'secret' => '**************************', 'trusted_domains' => array ( 0 => '192.168.0.16:444', 1 => 'nextcloud.protech.my', ), 'dbtype' => 'mysql', 'version' => '19.0.1.1', 'trusted_proxies' => ['letsencrypt'], 'overwrite.cli.url' => 'https://nextcloud.protech.my', 'overwritehost' => 'nextcloud.protech.my', 'overwriteprotocol' => 'https', 'dbname' => 'nextcloud', 'dbhost' => '192.168.0.16:3306', 'dbport' => '', 'dbtableprefix' => 'oc_', 'mysql.utf8mb4' => true, 'dbuser' => 'nextcloud', 'dbpassword' => '**********', 'installed' => true, ); # 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; client_max_body_size 0; location / { 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; proxy_max_temp_file_size 2048m; } }

@Danuel Alright. I tried your method but it is still stuck at the Let's Encrypt Web UI. I have try to remove let's encrypt docker and reinstall it. And the outcome still remain the same. I think I can concluded is not the let's encrypt issue. Do you think I should reinstall NextCloud docker? I hope it won't lost all the setting I made in the NextCloud. If so, it doesn't really matter, there is nothing important.

Can anyone show how you did the configuration for the nextcloud configuration file. I attached nextcloud conf. file for reference if anyone could tell me if I did any mistake. <?php $CONFIG = array ( 'memcache.local' => '\\OC\\Memcache\\APCu', 'datadirectory' => '/data', 'instanceid' => '*********************', 'passwordsalt' => '********************************', 'secret' => '*****************************', 'trusted_domains' => array ( 0 => '192.168.0.16:444', 1 => 'nextcloud.protech.my', ), 'dbtype' => 'mysql', 'version' => '19.0.1.1', 'trusted_proxies' => array ( 0 => 'letsencrypt', ), 'overwrite.cli.url' => 'https://nextcloud.protech.my/', 'overwritehost' => 'nextcloud.protech.my', 'overwriteprotocol' => 'https', 'dbname' => 'nextcloud', 'dbhost' => '192.168.0.16:3306', 'dbport' => '', 'dbtableprefix' => 'oc_', 'mysql.utf8mb4' => true, 'dbuser' => 'nextcloud', 'dbpassword' => '***************', 'installed' => true, 'maintenance' => false, );

@Danuel [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. s6-svwait: fatal: supervisor died [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 01-envfile: executing... [cont-init.d] 01-envfile: exited 0. [cont-init.d] 10-adduser: executing... usermod: no changes ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io ------------------------------------- To support the app dev(s) visit: Certbot: https://supporters.eff.org/donate/support-work-on-certbot To support LSIO projects visit: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... using keys found in /config/keys [cont-init.d] 30-keygen: exited 0. [cont-init.d] 50-config: executing... Variables set: PUID=99 PGID=100 TZ=************ URL=protech.my SUBDOMAINS=wildcard EXTRA_DOMAINS= ONLY_SUBDOMAINS=false VALIDATION=dns DNSPLUGIN=cloudflare EMAIL=*******@gmail.com STAGING= SUBDOMAINS entered, processing Wildcard cert for protech.my will be requested E-mail address entered: ********@gmail.com dns validation via cloudflare plugin is selected Certificate exists; parameters unchanged; starting nginx Starting 2019/12/30, GeoIP2 databases require personal license key to download. Please retrieve a free license key from MaxMind, and add a new env variable "MAXMINDDB_LICENSE_KEY", set to your license key. [cont-init.d] 50-config: exited 0. [cont-init.d] 60-renew: executing... The cert does not expire within the next day. Letting the cron script handle the renewal attempts overnight (2:08am). [cont-init.d] 60-renew: exited 0. [cont-init.d] 99-custom-files: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-files: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html) Server ready

@LoneTraveler I did not use CNAME. Instead, I used CloudflareDDNS docker by oznu to track my public IP. It generate an A record for me. Here the thing, I port forward to my NextCloud port number and it would work just fine. I have setup all the admin accounts until i realised it did not pass through the Let's Encrypt. What could be the issue that Let's Encrypt is not directing me to NextCloud?

@testdasi@Danuel I just release I didn't pass the NextCloud thru Let's Encrypt. Basically, I port forwarded directly to my Nextcloud IP. that why it work. Could you guys share me your nextcloud.subdomain.conf file how you guys configure? I tried exactly like the spaceInvader video but it is not working. It always stuck at the Let's Encrypt web UI only. I have posted in the Let's Encrypt support forum already. But if you guys got a sample you could share it would be helpful for me to learn.

Guys, I need help on how to configurate the nextcloud.subdomain.conf? I followed the SpaceInvader video but it is still stuck in the Let's Encrypt webpage.

I followed the SpaceInvader video for setting up OnlyOffice. However at the very last step when I click save, an error pop out and say "Error when trying to connect (bad healthcheck status". I did tried to remove the cert and key file and recopy again but still not working. I am still a newbie. Could anyone tell me what is the problem? I have copy and paste my conf file below for referrence as well: - # only office doc server server { listen 443 ssl; server_name onlyoffice.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_docs OnlyOfficeDocumentServer; proxy_pass https://$upstream_docs:443; proxy_redirect off; 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-Host $server_name; proxy_set_header X-Forwarded-Proto $scheme; } }

@Maggi0r I am having the same problem. Could you share your steps which folder you deleted in appdata and how you proceed from there?