Unable to access truenas web gui remotely i can ping the server from remote i tried wireguard and then tailscale both are giving same problem tunnel is up in both the plateform however nothing accessible

unable to access truenas web gui remotely i can ping the server (192.168.1.11) from remote i tried wireguard and then tailscale both are giving same problem tunnel is up i see sent/receive byte in both the plateform however nothing accessible. no firewall configured neither in truenas nor in my isp router nothing blocking i can access the internet from truenas scale each time tunnel is connected however when try to access server web GUI ( This site can’t be reached 192.168.1.11 refused to connect.) whereas i can access all the smb shares locally and server web GUI . i have port forwarding enable on router for port 51821 and 51820 UDP even after loss hope i did port forwarding for 80 and 443 and 445 also i know it does not make sense i tried everything possible however none of them working earlier the same thing was working with same wireguard

here is wireguard config for client

[Interface]
PrivateKey = 2L/Bb0HIP
Address = 10.8.0.2/24, fdcc:ad94:bacf:61a4::cafe:2/112
DNS = 1.1.1.1, 2606:4700:4700::1111
MTU = 1420

[Peer]
PublicKey = dTjsyurqnfZ
PresharedKey = /zBNpRPhfJU
AllowedIPs = 10.8.0.0/24
PersistentKeepalive = 0
Endpoint = 103.xyz.ysy.sas:portme

EDIT to alter the KEY data.

And

That’s probably the issue.

Also, you have published your keys and endpoint address to everyone.

how can i remove the keys from my post now i could not find way out

You should be able to edit your post, the button looks like a pencil. Though, I would create new keys.

no pencil button under my post in fact when try to delete it not allowing me to delete asking to contact administrator

Posting edited, you are safe for now.

1 Like

any body please help drowning in headache because of this

C:\Users\dell>ping 192.168.1.11

Pinging 192.168.1.11 with 32 bytes of data:
Reply from 192.168.1.11: bytes=32 time<1ms TTL=128
Reply from 192.168.1.11: bytes=32 time<1ms TTL=128
Reply from 192.168.1.11: bytes=32 time<1ms TTL=128
Reply from 192.168.1.11: bytes=32 time=1ms TTL=128

Ping statistics for 192.168.1.11:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms

C:\Users\dell>

server is pinging remotly however no access to web GUI local it working fine

Don’t know about Wireguard specifically but for Tailscale, you need to have Tailscale app installed on the Truenas server and have the Tailscale app installed (download app for your operating system from Tailscale site) on any computer you wish to access the Truenas server from. The computer used to access the Truenas server will then use the Tailscale address of the Truenas server. You must use the Tailscale network names or the remote ip addresses to access the server or it will not work. I also have the Truenas server set to be a Tailscale exit node in case I need to access something that I need to make think I am at home.

When working remotely I generally use the server name as it appears in the Tailscale Machines list in my Tailscale account. So if my server appears in the Tailscale list as truenas-scale-myserver then that is what I would use to access the server GUI remotely by. If I need access to a port for an app on the Truenas server, I just add the port number like so: (https:// truenas-scale-myserver:portnumber)

AllowedIPs = 10.8.0.0/24

Your Wireguard tunnel only allows routing of the 10.8.0.0/24 network, so you cannot connect to 192.168.0.0/24 network. You would need to use the server’s Wireguard IP, which I assume would be 10.8.0.1.

If you are using Tailscale, then you would need to connect to whichever IP Tailscale sets the server to (likely 100.x.x.x) or you can also use the MagicDNS name (usually machinename.tailabc123.ts.net format). You can use 192.168.0.0/24 network provided that you set the tailscale node which the server resides in as an exist node and ip forwarding is enabled on that tailscale client, but that is typically an advanced setup.

It seems to me that you need a networking primer, to be honest.

even if i use allowed ips 0.0.0.0/0 instead of 10.8.0.0/24 its not working

2025-09-17 22:20:35.841: [TUN] [wg] Creating network adapter
2025-09-17 22:20:36.467: [TUN] [wg] Using existing driver 0.10
2025-09-17 22:20:36.475: [TUN] [wg] Creating adapter
2025-09-17 22:20:36.791: [TUN] [wg] Using WireGuardNT/0.10
2025-09-17 22:20:36.791: [TUN] [wg] Enabling firewall rules
2025-09-17 22:20:36.654: [TUN] [wg] Interface created
2025-09-17 22:20:36.847: [TUN] [wg] Dropping privileges
2025-09-17 22:20:36.847: [TUN] [wg] Setting interface configuration
2025-09-17 22:20:36.847: [TUN] [wg] Peer 1 created
2025-09-17 22:20:36.855: [TUN] [wg] Setting device v4 addresses
2025-09-17 22:20:36.855: [TUN] [wg] Interface up
2025-09-17 22:20:36.875: [TUN] [wg] Sending handshake initiation to peer 1 (103.7:51821)
2025-09-17 22:20:36.976: [TUN] [wg] Setting device v6 addresses
2025-09-17 22:20:36.977: [TUN] [wg] Warning: the “Wi-Fi” interface has Forwarding/WeakHostSend enabled, which will cause routing loops
2025-09-17 22:20:36.986: [TUN] [wg] Startup complete
2025-09-17 22:20:41.891: [TUN] [wg] Sending handshake initiation to peer 1 (103.7:51821)
2025-09-17 22:20:46.931: [TUN] [wg] Handshake for peer 1 (103.7:51821) did not complete after 5 seconds, retrying (try 2)
2025-09-17 22:20:46.931: [TUN] [wg] Sending handshake initiation to peer 1 (103.7:51821)

this is logs of wireguard when it was working

2025-09-01 21:37:12.238 [TUN] [abhinav] Using existing driver 0.10
2025-09-01 21:37:12.247 [TUN] [abhinav] Creating adapter
2025-09-01 21:37:12.530 [TUN] [abhinav] Using WireGuardNT/0.10
2025-09-01 21:37:12.530 [TUN] [abhinav] Enabling firewall rules
2025-09-01 21:37:12.436 [TUN] [abhinav] Interface created
2025-09-01 21:37:12.547 [TUN] [abhinav] Dropping privileges
2025-09-01 21:37:12.547 [TUN] [abhinav] Setting interface configuration
2025-09-01 21:37:12.548 [TUN] [abhinav] Peer 1 created
2025-09-01 21:37:12.560 [TUN] [abhinav] Setting device v4 addresses
2025-09-01 21:37:12.560 [TUN] [abhinav] Interface up
2025-09-01 21:37:12.661 [TUN] [abhinav] Sending handshake initiation to peer 1 (103.47:51821)
2025-09-01 21:37:12.695 [TUN] [abhinav] Setting device v6 addresses
2025-09-01 21:37:12.738 [TUN] [abhinav] Startup complete
2025-09-01 21:37:12.817 [TUN] [abhinav] Receiving handshake response from peer 1 (103.7:51821)
2025-09-01 21:37:12.817 [TUN] [abhinav] Keypair 1 created for peer 1
2025-09-01 21:37:23.022 [TUN] [abhinav] Receiving keepalive packet from peer 1 (103.7:51821)
2025-09-01 21:37:53.218 [TUN] [abhinav] Receiving keepalive packet from peer 1 (103.7:51821)
2025-09-01 21:38:05.418 [TUN] [abhinav] Shutting down
2025-09-01 21:38:05.461 [MGR] [abhinav] Tunnel service tracker finished

**

i can see the wireguard logs says its connecting however i can not access the truenas server 192.168,1.11

**
2025-09-17 22:53:35.911 [TUN] [wg] Shutting down
2025-09-17 22:53:35.913 [MGR] [wg] Tunnel service tracker finished
2025-09-17 22:59:15.689 [TUN] [wg] Starting WireGuard/0.5.3 (Windows 10.0.19045; amd64)
2025-09-17 22:59:15.689 [TUN] [wg] Watching network interfaces
2025-09-17 22:59:15.692 [TUN] [wg] Resolving DNS names
2025-09-17 22:59:15.692 [TUN] [wg] Creating network adapter
2025-09-17 22:59:16.225 [TUN] [wg] Using existing driver 0.10
2025-09-17 22:59:16.235 [TUN] [wg] Creating adapter
2025-09-17 22:59:16.585 [TUN] [wg] Using WireGuardNT/0.10
2025-09-17 22:59:16.585 [TUN] [wg] Enabling firewall rules
2025-09-17 22:59:16.476 [TUN] [wg] Interface created
2025-09-17 22:59:16.606 [TUN] [wg] Dropping privileges
2025-09-17 22:59:16.606 [TUN] [wg] Setting interface configuration
2025-09-17 22:59:16.609 [TUN] [wg] Peer 1 created
2025-09-17 22:59:16.612 [TUN] [wg] Setting device v6 addresses
2025-09-17 22:59:16.612 [TUN] [wg] Interface up
2025-09-17 22:59:16.613 [TUN] [wg] Sending handshake initiation to peer 1 (103.17:51821)
2025-09-17 22:59:16.644 [TUN] [wg] Setting device v4 addresses
2025-09-17 22:59:16.694 [TUN] [wg] Startup complete
2025-09-17 22:59:16.736 [TUN] [wg] Receiving handshake response from peer 1 (103.7:51821)
2025-09-17 22:59:16.736 [TUN] [wg] Keypair 1 created for peer 1

@Rajesh_Agrawal

Please stop publishing your private keys, or deal with the consequences of possible hackers accessing your data.

1 Like

Glad you were able to solve it! :partying_face:

how to delete my either original post orm edit to remove something in that

unable to do it with pencil button nor any deletion button

please help me administrator to remove my original post public ip i exposed

I already helped yesterday when I made some changes to a few of your postings to keep your system safe. You may consider generating a new set of keys.