Cant get letsencrypt working on port other than 443 about nextcloudpi

[nachoparker]

Hi,
Good job.

You are supposed to enter the domain that you got from noip in the letsencrypt section of nextcloudpi-config.

Could you try the process again and paste here those errors?

One question... did you open the ports yourself, or through nextcloudpi-config?

I have not tried the URL cloacking... will look at it. EDIT: is it "mask URL" here?

[deljones]

Hi there... Thanks for your quick reply...

So I start port forwarding in raspi-config. To start with my 4th trusted domain in my NC config is my public address and port number. I'm using 8888 because 443 is used by my NAS. the 8888 is redirected to 443.

So that's all good... I switched off upnp as instructed on my modem. Created the service, NCBox on 8888 then on the firewall opened 8888 pointing to the NCBox. I can reach the server outside using public the address and inside using the LAN ip. I created a hostname at noip pointing to my public address which works except I have to have the 'Mask URL' unchecked otherwise I get a blank page. The masking of the URL is supposed to hide your public address and only show the hostname blah blah blah....

Regarding letsencrypt..
Started the utility in raspi-config

Entered the hostname, email address of my account. After a while I get this...

When I press 'Any key' the no-ip hostname has overwritten trusted domain 4 in my NC config, which it is supposed to do which was my public address and port number with the new hostname

I think I've done everything right?

D

[nachoparker]

Hi, I'm back

Well, you are trying to use let's encrypt with a non-standard port. Only port 443 for HTTPS works for Let's Encrypt for security reasons. Here is the info and the vulnerability

If you think about it, Let's encrypt is expecting to access your NextCloudPi on 443 but in your case 443 is the NAS. That is why it times out

See the explanation here

It seems like you will have to use the DNS challenge for that, which is more involved.

I'll close it but we can continue talking ;)

[deljones]

Hi Yes I am a dope!! I realised what I had done but I also did something else completely dumb... my noip hostname was set as a 'URL', ie redirect rather than an 'A' record. I ran the letsencrypt script again once I had corrected that small error and it worked... I now have a fully working secured instance at digitalcarnage.webhop.me..... Sadly I had to reinstall the instance 3 times today. If I move either of the swapfile or Dbase to my external drive I get a blank error 500 page on reboot :( The current build has everything on a fast 16G SD card except the ncdata which is on an external USB drive... Thanks ever so much for you help and understanding. I can tell you that in the past 36 hours I have leant so much thanks to you and this project... Its been a time vampire :) Keep it up Del

…

------ Original Message ------ From: "nachoparker" <[email protected]> To: "nextcloud/nextcloudpi" <[email protected]> Cc: "deljones" <[email protected]>; "Author" <[email protected]>

Sent: 09/07/2017 19:05:33 Subject: Re: [nextcloud/nextcloudpi] Cant get letsencrypt working (#43) Closed #43 <#43>. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#43 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACU9D34Coce2XNyj5aMoh0MHa9yXu3OWks5sMRZtgaJpZM4OQ26g>.

[nachoparker]

The USB drive needs to be on and responsive at all times... no sleeping, no stand by. See #15
Haha, imagine how much time this is consuming for me 😃