# Wireguard request put error - connection disconnect
**URL:** https://forum.pritunl.com/t/wireguard-request-put-error-connection-disconnect/3599
**Category:** Pritunl VPN
**Tags:** pritunl, pritunl-client
**Created:** [October 28, 2025, 6:50pm UTC](https://forum.pritunl.com/t/wireguard-request-put-error-connection-disconnect/3599 "2025-10-28T18:50:11Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@freefallcohesive](https://forum.pritunl.com/u/freefallcohesive)
#### Post date: [October 28, 2025, 6:50pm UTC](https://forum.pritunl.com/t/wireguard-request-put-error-connection-disconnect/3599/1 "2025-10-28T18:50:11Z")
My server pritunl-web daemon is set up behind a reverse proxy. I know this isn’t documented on the load balancing page but I changed the /etc/pritunl.conf bind\_addr to 127.0.0.1 since I wanted to use the reverse proxy instead, but I found that when connecting with wireguard the client attempts to reach the server at the internal gateway IP address on the “app.server\_port” setting port. This obviously doesn’t work and the client times out, and changing the bind\_addr back to “0.0.0.0” works again. I’m curious why the client doesn’t use the public IP/hostname setting instead. Is there a setting I’m missing somewhere to make the localhost binding work? I do have the public and sync address set in the host settings for this server.
---
### Author:  [@zach](https://forum.pritunl.com/u/zach)
#### Post date: [October 29, 2025, 12:53pm UTC](https://forum.pritunl.com/t/wireguard-request-put-error-connection-disconnect/3599/2 "2025-10-29T12:53:02Z")
Follow the [**load balancing documentation**](https://docs.pritunl.com/kb/vpn/system/load-balancing) for configuring a reverse proxy.
---
### Author:  [@freefallcohesive](https://forum.pritunl.com/u/freefallcohesive)
#### Post date: [October 29, 2025, 3:04pm UTC](https://forum.pritunl.com/t/wireguard-request-put-error-connection-disconnect/3599/3 "2025-10-29T15:04:41Z")
Hi Zach, I have read that page but this is more about the client and wireguard connections specifically.
The client attempts to communicate with the server on the configured app.server\_port and internal gateway IP even when there’s a reverse proxy configured. If I bind this port to localhost only the client isn’t able to do that and the wireguard connections time out.
---
### Author:  [@zach](https://forum.pritunl.com/u/zach)
#### Post date: [October 29, 2025, 4:58pm UTC](https://forum.pritunl.com/t/wireguard-request-put-error-connection-disconnect/3599/4 "2025-10-29T16:58:59Z")
The reverse proxy option must be enabled with `sudo pritunl set app.reverse_proxy true` and the client profile must be re-imported.
---
### Author:  [@freefallcohesive](https://forum.pritunl.com/u/freefallcohesive)
#### Post date: [October 29, 2025, 5:07pm UTC](https://forum.pritunl.com/t/wireguard-request-put-error-connection-disconnect/3599/5 "2025-10-29T17:07:26Z")
That’s all set up and working. I can reach the web interface from the public address, the configurations sync, and I can authenticate with both connection types through the reverse proxy.
Here’s what appears in the service logs after I connect with wireguard if I bind the pritunl-web service to localhost:
`profile: Request put error`
`Put “http://172.16.5.1:8080/key/wg///”: dial tcp 172.16.5.1:8080: connectex: No connection could be made because the target machine actively refused it.`