root@d13659a46c68:/var/log# snap install --classic certbot
error: cannot communicate with server: Post "http://localhost/v2/snaps/certbot": dial unix /run/snapd.socket: connect: no such file or directory
Seems like the only hold up is your cable modem configuration.
It needs to be set to allow, and forward, port 443 [as it is allowing, and forwarding, port 80].
1 Like
Show:
sudo apt install snapd
snap --version
1 Like
Yeah, if I connect internally, with the private IP, it works.
Just have to fix the certbot now. I got the old one out, but the snap command errors on install.
snap 2.57.6-1+b5
snapd unavailable
series -
Looks broken, but I removed, rebooted, reinstalled, rebooted, and still the same.
I see no errors during install
OK, let's focus on:
1 Like
I did the same setup on their site as I did for 80. It's just not working. So I wont hear back probably till Monday.
What do you mean "on their site?
What type of connection do you have to the Internet?
1 Like
1G fiber, but it's residential.
I'm confined to my house after a surgery on my spine, so I decided to build out a network. I used to do this for a living, but it's bee a while. Cisco is easier to setup than TP-Link, just 10 times the cost.
Anyway, yeah, they will get back to me, at the earliest tomorrow. But I expect it'll be Monday. And the person answered when I called wanted to know if my forwarding was for a land line, or cell phone. So, there's that.
The TP-Link menus should be where to look/fix this access problem.
Somewhere in there... port 80 is getting through.
You need to do something similar for port 443.
Glad to hear that you can keep your spirits up with this stuff [most can't/won't go near it] 
Cheers from Miami 
1 Like
443 is open now, just hit.
1 Like
And now the site is up. Just need to fix the bot.
Yes it is! 
$ nmap -Pn -p80,443 rumplenj.com
Starting Nmap 7.80 ( https://nmap.org ) at 2024-02-26 02:47 UTC
Nmap scan report for rumplenj.com (69.125.208.53)
Host is up (0.090s latency).
rDNS record for 69.125.208.53: ool-457dd035.dyn.optonline.net
PORT STATE SERVICE
80/tcp open http
443/tcp open https
Nmap done: 1 IP address (1 host up) scanned in 0.18 seconds
1 Like
certbot?
1 Like
Yes, I get this on snap install:
error: cannot communicate with server: Post "http://localhost/v2/snaps/hello-world": dial unix /run/snapd.socket: connect: no such file or directory
I might put the old one back, lol.
2 Likes
Yeah, for now, just reinstall the apt version of certbot.
And show us whatever file(s) are in the /etc/letsencrypt/renewal/ folder.
1 Like
When you have time ...
Install snapd on Debian using the Snap Store | Snapcraft
1 Like
That fails the same way, some file/folder not found. I think it's this stripped down version I'm running on.
Put the old one back, reattached the certs, working fine. Leaving it alone, lol
Thanks so much to everybody for the help.
2 Likes
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.