can not access next cloud deployment

[khaledyoussef24]

after deploying next cloud and setting dns to the ip it gives site is not reachable

digging shows it points to the exact ip

[khaledyoussef24]

the same issue is on devnet and qa

[Mik-TF]

@khaledyoussef24 Thanks for creating the issue.

Did you wait a couple of minutes and retry? Or perhaps check with a dns checker to see if the propagation was 100% completed? I had this error "Site can't be reached" too when deploying and it resolved after a couple of minutes after dns propagation.

In the docs I wrote some info on dns checker so users can be warned that they might need to wait.

On some browsers it can be quicker. And clearing the cache might help too. For example with Tor it is always way quicker than with Firefox or Brave.

Let me know what you think and I could perhaps improve the docs.

[Mik-TF]

@khaledyoussef24

Just to be sure, as per the notice (see below) after deployment, you need to click on the Actions button Open Nextcloud that uses the url "domain.tld:8443" to set the Nextcloud instance.

(Notice: Successfully deployed a Nextcloud AIO instance. Make sure to add a DNS A record (Host: "@", Value: \<Public IPv4 Address>) to your domain. After DNS propagation, under Actions, click Open Nextcloud.)

I adjusted the documentation to make this as clear as possible.

Once the installation is done, users can use "domain.tld" without :8443 to connect to their admin login page.

[Mik-TF]

I did a quick test and it works after full propagation with :8443 port.

---

But to be clear, it won't work with threefold.pro without :8443 until the user sets the containers.

Before setting the containers:

Then you link the domain and start the containers

After setting the containers you can access threefold.pro/login to sign into nextcloud. So at this point, writing threefold.pro as a URL will lead to threefold.pro/login

Let me know what you think. I can put all these images in the documentation and explain the whole process if it would make this ultra clear.

[Mik-TF]

I updated the docs to take into account this issue. The steps are all laid out clearly now. See here

We will be able to close this issue once the nextcloud docs is published (PR is merged).

[Mik-TF]

The information from the documentation is now clear to show how to get the deployment running. I will close this issue.

Note that we will be updating the nextcloud weblet with gateway support. We will publish the docs and the new weblet when the gateway version is ready.

[khaledyoussef24]

i still can not deploy the solution i tried to deploy on devnet and qa i still get the same errors even the machine is not reachable it requires a password the domain points right into the machine

[Mik-TF]

@khaledyoussef24 Thanks for the work.

1. URL access: After deploying the VM with nextcloud weblet, you need to access the url with :8443 at the end (the Actions button "Open Nextcloud" does it automatically)

e.g.: khalednextgded.gridtest.xyz:8443 khalednextgded.gridtest.xyz without :8443 won't work.

I tested on test and dev net, and it works (with :8443).

2. Password: I think you had a different SSH public key in the playground for dev net, so it asked for a password. With the proper SSH pub key in Profile manager, it shouldn't ask for a password.

I tested with wrong pub key, and it asked for a password. I tested with correct pub key and it worked (doesn't ask for a password) and could ssh into the VM.

[Mik-TF]

Note: the new version of the Nextcloud weblet should be clearer when it comes to opening the URL with :8443. A clear message will be shown after deployment.

[khaledyoussef24]

khalednextgded.gridtest.xyz:8443 even after trying the port it can not be reached

I think this part should be documented

the ssh key is set right i even made deployments for vms and they are accessible easily so is there any other solution?

[Mik-TF]

This is strange. I am not sure how to troubleshoot it since it doesn't happen on my end.

The updated Nextcloud weblet with gateway will soon be available in a few days, perhaps we can test it then and see if this issue persists.

[khaledyoussef24]

@Mik-TF is there any updates and will the gateway update will fix the issue ?

[Mik-TF]

Sorry for the delay in this issue, the gateway version took lots of testing.

The nextcloud gateway update should be published as a PR this week.

The issue of SSH not working never happened in our testings, so it might not be an issue in the new version.

For the "site can't be reached", sometimes DNS propagation is very long, and this is documented in the new docs here.

So in a way, the two issues here (SSH, DNS) are most probably fixed (DNS issue is covered in docs, SSH issue never happened in our testing of new weblet). I will keep you posted on how it unfolds. Thank you for your time by the way.

[Mik-TF]

@khaledyoussef24

If I may add: the original issue isn't about SSH issue, but about DNS propagation and "site can't be reached".

Since we cover this in the nextcloud docs, I think we could consider this issue to be fixed.

We could test SSH in the new weblet version and make a new issue for this explicitly if it is still happening.

What do you think?