[2023-1-24 7:21:32][ERROR] Request: JSON parse failed
SyntaxError: Unexpected token ‘<’, "
"… is not valid JSON
SyntaxError: Unexpected token ‘<’, "
"… is not valid JSON
at JSON.parse ()
at Response.json (webpack-internal:///./app/Request.js:45:25)
at eval (webpack-internal:///./app/types/ProfileTypes.js:619:37)
at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
[2023-1-24 7:22:27][ERROR] Request: JSON parse failed
SyntaxError: Unexpected token ‘<’, "
"… is not valid JSON
SyntaxError: Unexpected token ‘<’, "
"… is not valid JSON
at JSON.parse ()
at Response.json (webpack-internal:///./app/Request.js:45:25)
at eval (webpack-internal:///./app/types/ProfileTypes.js:619:37)
at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
This was in the Client logs a few seconds after that entry (that I shared in orig post) went into the server specific log…
the closest errors in the service logs were from about half an hr earlier when I was still playing with some ovpn stuff…
This appears to be an error requesting the profile logs from the background service. Try deleting all log files in the C:\Users\USERNAME\AppData\Roaming\pritunl and C:\ProgramData\Pritunl directories. Then restart the computer or the Pritunl service. If this doesn’t work delete both the directories and import the profiles again.
[2023-1-30 6:43:59][ERROR] Request: JSON parse failed
SyntaxError: Unexpected token '<', "<html>
"... is not valid JSON
SyntaxError: Unexpected token '<', "<html>
"... is not valid JSON
at JSON.parse (<anonymous>)
at Response.json (webpack-internal:///./app/Request.js:45:25)
at eval (webpack-internal:///./app/types/ProfileTypes.js:619:37)
at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
[2023-1-30 6:44:42][ERROR] Request: JSON parse failed
SyntaxError: Unexpected token '<', "<html>
"... is not valid JSON
SyntaxError: Unexpected token '<', "<html>
"... is not valid JSON
at JSON.parse (<anonymous>)
at Response.json (webpack-internal:///./app/Request.js:45:25)
at eval (webpack-internal:///./app/types/ProfileTypes.js:619:37)
at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
I changed time zone on the server to make sure they match and same result… (howmany seconds of error would trigger an issue?) I’m puzzled why ovpn works fine but wg gives me the “failed to connect right away”, there is no log output on the server side that I see either… thanks for your help though!
WG is running on both server and client, I tried making a new server without 2FA, same result- fails as soon as I click the WG button and the logs show the error 405.
firewall clientside was also disabled, time on both server/client matches, ovpn works fine, both ports open on gateway serverside, no sign of the client reaching the server (no info in logs).
Also I noticed that the port number of the WG server isnt in the ovpn file - is it exchanged over the ovpn port or is the port number for wg not plaintext?
The connection and authentication process is detailed in the WireGuard documentation. The Pritunl Client will use the remotes and sync addresses from the configuration to send an authentication request to the HTTPS port of the Pritunl web server. This will generate a temporary WireGuard key for the duration of the connection. The client will need access to the Pritunl web server port for this to function.
If I want to use a subdomain with rev proxy to point to the pritunl web server, how would I make the client aware of what subdomain/url to use? edit the sync_hosts entry in the ovpn file?