Thread Rating:
  • 1 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[ Letsencrypt ][ 1.0.0.0 ] Free, automated, and open Certificate Authority.
#11
i'll have a look this evening
------------------------------------------------------------------------
[Image: linkedinbutton.jpg][Image: btn_donate_LG.gif]
Please respect my work and dont share my modules
Reply
#12
Thx!
I'm a noob regarding this, but to me it seems that it has something to do with python... So already tried to reinstall your python module, but with the same result...
Reply
#13
install letsencrypt module version 0.20.0.0 and let me know if still issue
------------------------------------------------------------------------
[Image: linkedinbutton.jpg][Image: btn_donate_LG.gif]
Please respect my work and dont share my modules
[-] The following 1 user says Thank You to outkastm for this post:
  • kos
Reply
#14
Module installed successfully.
Registration succeeded.
But upon creation of the certificates I got the message:
Problem binding to port 443: Could not bind to IPv4 or IPv6.
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:5000
no listening sockets available, shutting down
Unable to open logs.

Afterwards I was unable to connect to the admin page of my NAS, not via DNS, not via local IP and port number. Other ports are still accessible.

EDIT: after reboot of my NAS I could access it again #relieved

Ran the create certifates script again after the reboot and it worked.
Certificates have been created Smile
Reply
#15
and are you able to acces the admin page now ? letsencrypt have to use the port 443 during certificate creation. So during certificate creation will stop the thecus admin page and start it back after the certifcate has been created or renewed
------------------------------------------------------------------------
[Image: linkedinbutton.jpg][Image: btn_donate_LG.gif]
Please respect my work and dont share my modules
Reply
#16
x86 and x64 updated to 0.20.0.0
------------------------------------------------------------------------
[Image: linkedinbutton.jpg][Image: btn_donate_LG.gif]
Please respect my work and dont share my modules
Reply
#17
(02-01-2018, 11:43 PM)outkastm Wrote: and are you able to acces the admin page now ? letsencrypt have to use the port 443 during certificate creation. So during certificate creation will  stop the thecus admin page and start it back after the certifcate has been created or renewed

Yes, I'm able to access the admin page now.
So I will have to keep the portforwarding 443 active to my NAS ?
Reply
#18
yes, 443 should be always forwarded for auto renew. if you dont want to have remote access to your admin page, you have to change the port
------------------------------------------------------------------------
[Image: linkedinbutton.jpg][Image: btn_donate_LG.gif]
Please respect my work and dont share my modules
Reply
#19
I have been trying to secure my ownCloud access, but haven't succeeded yet. Besides altering the http-ssl config file, do you have to make more changes to get it working? Port forwarding on the router? Changes to ownCloud config file?
Reply
#20
Only change the http-ssl config file. Did you followed my guide ?
For sure you need to forward Owncloud port on your router. Certificate is valid when you access Owncloud through the domain for which you created the certificate.
------------------------------------------------------------------------
[Image: linkedinbutton.jpg][Image: btn_donate_LG.gif]
Please respect my work and dont share my modules
Reply


Forum Jump:


Users browsing this thread: 3 Guest(s)