Cannot connect to HP Remote System Controller through Tailscale

[james_lai]

Model: HP Remote System Controller
Firmware Version: 26.04.1

I have an HP Remote System Controller (RSC) with Tailscale VPN enabled.
The RSC is successfully connected to my Tailnet, and the device responds to both `tailscale ping` and standard Linux `ping`. However, accessing the admin console through the Tailnet results in a "connection refused" error.
I used `nc -zv` to check port 443 on the RSC's Tailscale IP. It also fails with a "connection refused" error. It appears no service is listening on the port at all.
Can I configure the web server to listen on both the LAN IP and the Tailscale IP?

[Kuroi_Kenshi]

Hi @james_lai,

Welcome to the HP Support Community!

Thanks for reaching out!

On HP Remote System Controller (RSC), the web UI and API are bound to the controller’s local network interfaces (Ethernet/VLAN) and exposed over HTTPS (port 443) using its configured IP/hostname and TLS certificate. Access patterns that work are, for example, the following:

• Direct LAN access to the RSC’s IP or hostname (IPv4/IPv6)
• Access via DNS names that resolve to those LAN IPs, with appropriate firewall rules

From the HP Remote System Controller User Guide, HTTPS access is described strictly in terms of the RSC’s own IP/hostname and browser-based access, with no mention of additional VPN interfaces such as Tailscale or routing web traffic over them. The controller’s network configuration focuses on:

• IPv4 / IPv6 addressing (Manual / DHCP)
• DNS server assignment
• Proxy settings
• VLANs
• 802.1x security
• Certificates for HTTPS and 802.1x
• Firewall/network requirements for HP Remote System Management cloud service

All web and API access is expected to go through those configured interfaces and the standard HTTPS server certificate. The guide does not document support for binding the HTTPS service to other virtual or overlay interfaces like Tailscale, nor for exposing the admin console over such VPNs. Instead, it assumes direct IP connectivity and standard firewall/NAT configuration on the LAN and toward HP’s cloud services.

Because of that, what you’re seeing is consistent with:

• Tailscale successfully reaching the RSC’s host at the network level (ICMP ping / Tailscale ping OK), but
• The RSC’s HTTPS listener not bound to or not reachable via the Tailscale-assigned interface, leading to “connection refused” when you try to hit port 443 on the Tailscale address.

In short:
RSC’s documented and supported access methods are via its configured LAN/VLAN IP (or hostname) and not via Tailscale VPN IPs, so HTTPS on the Tailnet address is expected to fail. To administer the RSC, use its LAN IP/hostname and standard browser access, optionally going through your own VPN that transparently routes to that LAN, rather than trying to use the RSC’s Tailscale endpoint as the HTTPS entry point.

If you need remote, secure access over the internet, HP’s recommended path is to:

• Configure RSC networking (IPv4/IPv6, DNS, proxy, VLAN, 802.1x as required)
• Configure certificates and strong passwords
• Enroll the RSC in HP Remote System Management (RSM) and access/manage it via HP’s cloud service, following the documented firewall and endpoint requirements.

I hope this helps

Take care and have an amazing day ahead! 🚀

Best regards,

Kuroi_Kenshi