Skip to main content

Test a CONNECT proxy before inserting it

POST 
/admin/settings/proxy/probe

Dials the candidate and issues CONNECT example.com:443. A successful probe is the gate the panel uses before appending the URL to the platform proxy list.

The error never echoes the URL. A paste that carried user:pass@ is refused as invalid, and a transport failure is sanitised to host and cause. Internal address literals are refused rather than dialled.

A shape error is 400. A proxy that is reachable as TCP but does not speak CONNECT is 200 with ok: false — the form has to show "this one is down" without it reading as a client error.

Permission: super-user. The list is the install's geo-egress path.

Request​

Responses​

Whether CONNECT succeeded