Thanks for providing valuable inputs for setting up the nextcloud with the Lets encrypt , well for me this is the first time I am setting it up and after installing couple of times , I am able to successfully create the certs and in the console I can see the message "server ready".
What I have done so far:-
- Install OMV5 and it is running on default port on Rasbian buster.
- Install docker using OMV-Extras
- Install Portainer and cockpit, working fine.
- Used the link <Nextcloud subdomain reverse proxy example> for preparing the compose.yml, with the letsencrypt port as ports:
- Pass thru all the errors and finally i can see the certs are created and I can see the message as server ready.
- Navigate thru the path of subdomain conf and rename the sample as .conf file, changed the server_name mydomain.*;
- Navigate thru \\<path>\appdata\nextcloud\config\www\nextcloud\config\config.php and added the following lines 'trusted_proxies' =>
0 => 'local ip:444', # This line may look different on your setup, don't modify it.
1 => 'nextcloud.mydomain name',
'overwrite.cli.url' => 'https://mydomain name/',
'overwritehost' => 'mydomain name',
'overwriteprotocol' => 'https',
- Post that restarted the nextcloud and letsencrypt container.
- And everytime when i try to access the URL as https://nextcloud.mydomain name/ , I am getting the message as Welcome to our serverThe website is currently being setup under this address.For help and support, please contact: firstname.lastname@example.org
2 questions :
how can i pass thru and should be able to login @ nextcloud, as I am not able to login even once
how can i access nextcloud from the local machine using local ip as whenever i tried as https://localip:444/ it is not working.
It seems like I am missing some trivial thing in this configuration, but not sure where.
please suggest...and shed some light on this...!!