I got a huge problem with CertBot

Help
21

There are two different things in play here:

  • Your DNS settings on no-ip for your hostname should point to your public IP address, so people from the world wide web can actually connect to you;
  • Your router should have two portmaps for port 80 and 443 to your local IP address, so it knows where to forward the connections from the world wide web to locally.
1 Like
22

oooooooooooo my website still works even i after i turned off port forwarding. so i guess ill see if i can change to my public ip on no ip.

23

Yes, but just for you, as only you can connect to your local computer. But all other 7 billion people on the internet can't.

Once you change the DNS settings of your hostname to your public IP address, you will need to port forwards too.

1 Like
24

okay, i got the port 80 and 443 open. im on my no ip and checking right now. try pinging my site and tell me if its a different ip.

25

okay, but during port forwarding, it wouldnt accept my public ip.

26

I can see a public IP address now indeed. Although it seems I can't connect to your webserver on port 80. Is it running?

That's because, as I said earlier, your router wants to know the local IP: it wants to know where to forward the connections to in your local network.

27

yes it is. but when i try to verify my service it just says connecting timed out. my apache is on right now.

28

See my edit in the previous post: your router requires the local IP address.

29

okay, right now my apache says port 80 in use by "unable to get info"

30

it says common application, which should i pick theres a lot of stuff like AIM, BGP, HTTP, HTTPS....

31

I don't know what that means, other than there already is an application listening on port 80.

That said, I still can't connect to that service listening on port 80.

32

well i have multiple devices open right so some people are playing video games could that be the problem?

33

Probably not, but if we're talking about people playing video games, I'm getting the feeling we're pretty much outside of the scope of this Community. I hoped it would be pretty simple and straightforward to help you with getting you a Let's Encrypt certificate, but it seems this thread keeps getting more and more of a generic "networking issue" problem. And if you'd ask me, such generic issues is pretty much outside the scope of this Community.

34

btw there is a lot of common application options, so ill just leave it blank for now.

35

okay. im going see if certbot works now that ive added port forwarding.

36

dude.... THANK YOU...... I opened certbot and guess what congrats your certificate and chain have been saved at ....................... SO THE WHOLE TIME I HAD TO CHANGE MY TO MY PUBLIC IP

1 Like
37

for some reason i dont see a lock near my website tho.

38

Probably because you used the certonly subcommand for certbot which does just that: only give you a cert. Afterwards, the cert would need to be installed into Apache manually. Please try this to do everything fully automated:

certbot --apache --keep

39

The requested apache plugin does not appear to be installed. ??

40

Oh, right, ignore that.. You're running on Windows. I think the Apache plugin doesn't work there..

You'll have to install the certificate you just got issued by hand into Apache.