@brianc1969 

Without my changing anything, ssh has stopped working... it partially loads the welcome message from the server, but never actually gives me a shell prompt... and it just sits there waiting.

I checked insights on the gateway and I see right around 40% memory usage and 2-4% cpu usage. Don't think I'm being constrained here.

External websites are still working. Ping still works (so DNS is still working).

Hi @brianc1969 

brianc1969 wrote

  @brianc1969 

Without my changing anything, ssh has stopped working... it partially loads the welcome message from the server, but never actually gives me a shell prompt... and it just sits there waiting.

I checked insights on the gateway and I see right around 40% memory usage and 2-4% cpu usage. Don't think I'm being constrained here.

External websites are still working. Ping still works (so DNS is still working).

Based on what you described, there seems to be nothing wrong.

VPN should be working.

For the web interface, you probably want to double-check the pi-hole interface. As it is not a domain name like <ip>:port. It requires the following lines:

With the /admin/, can you access it. Simply putting the IP in the URL does not get you connected to the web interface.

Hi  @brianc1969 

e.g. direct IP.

Correct URL:

  @Clive_A 
Thanks for the reply.

I was trying to describe that I cannot get anything to completely load. With piHole as the example, it works from a name from within my network. But via the VPN, I cannot get the control page to load, either with a name or with just the IP. And yes, I am using the /admin. I can ping via name, which tells me the VPN is resolving DNS, so names should work.

Another example is my homeassistant webpage. It is on a different port, on a different IP. Again, it works via name or IP locally, but never loads either way via VPN.

And a third example, I run a local webserver, which again is available via name or IP on standard port 80 on yet another machine. Again, I cannot get that to load via VPN.

Additionally, as I stated in my second post, at this time, SSH only loads part of the welcome message and never allows me to connect to any machine on my network, even though this worked initially.

The fact that I get part of the welcome message tells me the VPN made the connection. But for some reason I cannot complete it.

Hi @brianc1969 

Thanks for posting in our business forum.

brianc1969 wrote

  @Clive_A 
Thanks for the reply.

 

I was trying to describe that I cannot get anything to completely load. With piHole as the example, it works from a name from within my network. But via the VPN, I cannot get the control page to load, either with a name or with just the IP. And yes, I am using the /admin. I can ping via name, which tells me the VPN is resolving DNS, so names should work.

 

Another example is my homeassistant webpage. It is on a different port, on a different IP. Again, it works via name or IP locally, but never loads either way via VPN.

 

And a third example, I run a local webserver, which again is available via name or IP on standard port 80 on yet another machine. Again, I cannot get that to load via VPN.

 

Additionally, as I stated in my second post, at this time, SSH only loads part of the welcome message and never allows me to connect to any machine on my network, even though this worked initially.

 

The fact that I get part of the welcome message tells me the VPN made the connection. But for some reason I cannot complete it.

If it worked before, it should do the same now.

Did you change any parameters in the Wireguard peer?

If you can do a self-examination, that would be great. We have guides on how-to Wireguard setup.

You can delete the existing Wireguard and create it again and test it out one more time. If this persists, please paste your parameters and a simple network diagram.

Please mosaic your sensitive information. Here is a list of information considered sensitive:

1. Public IP address on your WAN if your WAN is.

2. Real MAC address of your device.

3. Your personal information including address, domain name, and credentials.

For troubleshooting purposes, when a WAN IP is needed, please leave some values visible for identification.