You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With a recent Vite upgrade, it is no longer possible to reach the Vite dev server with any hostname other than 'localhost' unless that host is configured in vite.config.js.
As vite.config.js is not user configurable, this means Evidence cannot be used in dev mode at all outside of localhost, nor can development builds be tested on anything other than local machines.
Steps to Reproduce
Run evidence in dev mode, then try to reach the site with a custom hostname. This can be reproduced with the following CURL command:
curl -vvvv localhost:3000 -H "Host: example.com"
Logs
% curl -vvvv localhost:3000 -H "Host: example.com"* Host localhost:3000 was resolved.
* IPv6: ::1
* IPv4: 127.0.0.1
* Trying [::1]:3000...
* Connected to localhost (::1) port 3000
> GET / HTTP/1.1
> Host: example.com
> User-Agent: curl/8.7.1
> Accept: */*>* Request completely sent off
< HTTP/1.1 403 Forbidden
< Access-Control-Allow-Origin: *< Content-Type: text/plain
< Date: Fri, 07 Mar 2025 00:15:49 GMT
< Connection: keep-alive
< Keep-Alive: timeout=5
< Transfer-Encoding: chunked
<
Blocked request. This host ("example.com") is not allowed.
* Connection #0 to host localhost left intact
To allow this host, add "example.com" to `server.allowedHosts`in vite.config.js.%
System Info
Severity
annoyance
Additional Information, or Workarounds
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
With a recent Vite upgrade, it is no longer possible to reach the Vite dev server with any hostname other than 'localhost' unless that host is configured in vite.config.js.
As vite.config.js is not user configurable, this means Evidence cannot be used in dev mode at all outside of localhost, nor can development builds be tested on anything other than local machines.
Steps to Reproduce
Run evidence in dev mode, then try to reach the site with a custom hostname. This can be reproduced with the following CURL command:
curl -vvvv localhost:3000 -H "Host: example.com"
Logs
System Info
Severity
annoyance
Additional Information, or Workarounds
No response
The text was updated successfully, but these errors were encountered: