Help me to configure nextcloud vm

KxOphA · November 16, 2019, 3:17pm

Hello,

I tried the configuration from VMware … I had some problems.
So I bought the Hyper-V version of Hanssonit.se .

Having never been able to configure properly … I finally returned to VMware.
I have no idea if the configuration of good or not currently, I am a regular at windows … linux is my first experience (for life).
So I go around in circles without result for 3 days.

I can access nextcloud from this address: 192.168.1.36.
My domain name does not join this IP address …
locally if i try to access nextcloud i get this error:
Access from an untrusted domain.

Although I read the documentation … I have no idea how to fix it all …
In short, what is super simple for some is an impossible mission for me.
To say that I thought I could set up nextcloud for my party, I must admit that the gift I wanted to make is bitter at the moment …

In short, if a charitable soul could help me … guide me … or take control at a distance (whatever), I want my nextcloud to be functional one day … and here I am at the edge of the agony.

KarlF12 · November 16, 2019, 3:30pm

Are you comfortable with Ubuntu at all? If so, install via Docker or snap are both pretty easy.

Reiner_Nippes · November 16, 2019, 3:42pm

We had this here:

KxOphA · November 16, 2019, 3:44pm

really not, i was never able to complete the installation. so i reinstall back W10 pro.
My first idea was to put a clean and fresh install of ubuntu, but just the install break my head… #noobian here powered by windows

KxOphA · November 16, 2019, 3:46pm

the bad thing is…i understand nothing in that.
I use MS environment for too long and we cannot install nextcloud server directly on windows.
So i feel like to be at my first day in class.

KxOphA · November 16, 2019, 4:40pm

I’ve tried :

sudo docker exec --user www-data nextcloud php occ overwrite.cli.url --value=https://disque.fiasko.ca

And the result was:

sudo: docker: command not found

As i said i use the Nextcloud VM - by T&M Hansson IT on vmware (actually).
I had no idea how to change things to make possible to reach my nextcloud.

Reiner_Nippes · November 16, 2019, 6:06pm

sorry. in a non-docker environment it should be:

sudo -u www-data php /var/www/html/occ overwrite.cli.url --value=https://disque.fiasko.ca

where /var/www/html/occ depends on your installation. could be also /var/www/html/nextcloud/occ. in case of doubt find /var -name occ or locate occ.

to fix the trusted domain problem:
sudo -u www-data php /var/www/html/occ config:system:set trusted_domains 2 --value=disque.fiasko.ca

where the “2” depends on the number of entries already in your config.php file. the config.php is in the folder config in the folder where you found occ.

or you run sudo -u www-data php /var/www/html/occ config:system:get trusted_domains

KxOphA · November 16, 2019, 6:26pm

I restarted all the process and now i can access nc in local.
In external like disque.fiasko.ca give me a 522 error by cloudflare. i try to investigate that now…

During onlyoffice installation i received this error (just now)

Reiner_Nippes · November 16, 2019, 6:56pm

There is an issue with cloudflare. It won’t work. You can find issues about this here in the forum and in the nextcloud documentation online.

KxOphA · November 16, 2019, 7:25pm

bah nothing work at all (except in local using 192.168.1.XXX).

Using my domain name the page could not be reach.
At the end of configuration system told me to change login.
I changed it and till this time i cannot login in the terminal…

KxOphA · November 17, 2019, 3:02pm

little update: nextcloud run well in local.
My ISP block ports 80 and 443.
So i subscribed to no-ip.
my domain name --> public IP:51290 --> Router DMZ (192.168.1.51) --> Nextcloud VM internal IP (192.168.1.100).
ports 80, 443, 51290 open in W10 firewall.
if i do a séarch for ports open…all are listed “closed or blocked”…
Whàt can i do to resolve this last problem?

KarlF12 · November 17, 2019, 3:17pm

I think there is still some confusion here… you should have no need to open ports on a Windows 10 client.

Please explain your setup in detail.

Reiner_Nippes · November 17, 2019, 4:51pm

that means: “we don’t want you to run servers at home.”

in your case you need “DNS-01 challenges” to get a letsencrypt cert.

first: ask google if that’s possible with no-ip.com.

daniel (@enoch85) has implemented this method in his scripts. so you my ask him who to set it up correctly.

github.com

nextcloud/vm/blob/169058970362c6bcebdc357435794feaf82f1a58/lets-encrypt/activate-ssl.sh#L221


      
          fi
          }
          tls-alpn-01() {
          if eval "certbot certonly --preferred-challenges tls-alpn-01 $default_le"
          then
              echo "success" > /tmp/le_test
          else
              echo "fail" > /tmp/le_test
          fi
          }
          dns() {
          if eval "certbot certonly --manual --manual-public-ip-logging-ok --preferred-challenges dns $default_le"
          then
              echo "success" > /tmp/le_test
          else
              echo "fail" > /tmp/le_test
          fi
          }
          
          methods=(standalone dns)

you may experiment a bit on the command line with

certbot certonly --manual --manual-public-ip-logging-ok --preferred-challenges dns  --rsa-key-size 4096 --renew-by-default --no-eff-email --agree-tos --uir --hsts --server https://acme-v02.api.letsencrypt.org/directory -d disque.fiasko.ca
# or 
certbot certonly --manual --manual-public-ip-logging-ok --preferred-challenges dns  --rsa-key-size 4096 --renew-by-default --no-eff-email --agree-tos --uir --hsts --server https://acme-v02.api.letsencrypt.org/directory -d office.fiasko.ca

and check the certbot manual how dns-01 challenge is working.

if you got that working, you have to change the apache config so that apache/nextcloud is no longer listening on port 443 but on 51290.

github.com

nextcloud/vm/blob/169058970362c6bcebdc357435794feaf82f1a58/lets-encrypt/activate-ssl.sh#L123


      
          then
              touch "$ssl_conf"
              print_text_in_color "$IGreen" "$ssl_conf was successfully created."
              sleep 2
              cat << SSL_CREATE > "$ssl_conf"
          <VirtualHost *:80>
              ServerName $domain
              Redirect / https://$domain
          </VirtualHost>
          
          <VirtualHost *:443>
          
              Header add Strict-Transport-Security: "max-age=15768000;includeSubdomains"
              SSLEngine on
              SSLCompression off
              SSLProtocol all -SSLv2 -SSLv3
              SSLCipherSuite ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA:ECDHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES256-SHA:ECDHE-ECDSA-DES-CBC3-SHA:ECDHE-RSA-DES-CBC3-SHA:EDH-RSA-DES-CBC3-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:DES-CBC3-SHA:!DSS
              SSLHonorCipherOrder on
              
          ### YOUR SERVER ADDRESS ###

KxOphA · November 17, 2019, 5:07pm

Funny fact…everything work except only office.
funny fact #2: trying to reach your server when vmware is closed is a bad idea…

So, my paid hyper-V vm will never be used…

KxOphA · November 18, 2019, 2:55pm

Now i have to find a way to take control of terminal.
Since they ask to change the username and password, i cant access anymore the terminal.

Reiner_Nippes · November 18, 2019, 5:20pm

enoch85 · November 18, 2019, 7:31pm

https://docs.hanssonit.se/s/W6fMouPiqQz3_Mog/virtual-machines-vm/d/W6fMquPiqQz3_Moi/nextcloud-vm-first-setup-instructions

KxOphA · November 25, 2019, 3:24pm

Thanks, everything work with VMware !