Failed to open TCP connection to localhost:3036 #89
-
Description 📖Hello, I've been trying to migrate a Rails app from webpacker to vite-rails, and while everything works with the I unfortunately could not reproduce this error on a new project so it is likely to be an issue with something else on my app that's not letting Rails connect to the vite dev server for some reason. But other connections are working fine (like to While this may not be an issue with vite_ruby/vite_rails itself, would anyone know what could possibly be going wrong with my setup? I have tried not running most extra middleware and most things from the initializers folders that's not default by Rails, also with no success. Reproduction 🐞Vite Ruby InfoRun Logs 📜Vite dev server itself seems to run just fine with seemingly nothing wrong on logs If not providing a reproduction: OutputRun Rails error logsvite.config.ts and vite.jsonimport { resolve } from 'path'
import { defineConfig } from 'vite'
import RubyPlugin from 'vite-plugin-ruby'
export default defineConfig({
plugins: [RubyPlugin()],
resolve: {
alias: {
'@': resolve(__dirname, 'app/javascript/entrypoints'),
'@assets': resolve(__dirname, 'app/assets')
}
}
}){
"all": {
"sourceCodeDir": "app/javascript",
"watchAdditionalPaths": []
},
"development": {
"publicOutputDir": "vite-dev",
"port": 3036,
"autoBuild": true, // I have also tried using not using autoBuild
"devServerConnectTimeout": 3 // I have tried a lot of different timeouts, and using the default one, with no success
},
"test": {
"autoBuild": true,
"publicOutputDir": "vite-test"
}
}Screenshots 📷Provide console or browser screenshots of the problem.
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 12 replies
-
|
Hi John Victor! Nothing unusual in the config, except that it might be better to be explicit with the alias: {
'@/': `${resolve(__dirname, 'app/javascript/entrypoints')}/`,Otherwise it could interfere with certain imports such as Based on the Rails error logs, it seems that the Vite dev server is not reachable. You'll want to verify this from a Rails console, by using
What is the response if you |
Beta Was this translation helpful? Give feedback.
-
|
PS: @johnvictorfs Moved it to Discussions, since it's likely to be a problem in how the project is configured. |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
@johnvictorfs Let's try a few things.
If you are online, you can join the Vite.js Discord channel and I'll help you debug it. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, I can join the Discord in just a bit, thanks |
Beta Was this translation helpful? Give feedback.
-
|
The problem is related with a recent change in Vite, which affects systems where Configuring "development": {
"autoBuild": true,
"host": "127.0.0.1",
"publicOutputDir": "vite-dev",
"port": 3036
},I will evaluate changing the default from |
Beta Was this translation helpful? Give feedback.
-
|
Let's explore having this by default in Vite Ruby, I think the only downside would be for Docker setups, but that can be documented and it's less time consuming to debug than this. |
Beta Was this translation helpful? Give feedback.
-
|
If Docker is a concern, would there be any harm in defaulting it to |
Beta Was this translation helpful? Give feedback.
-
|
Users now have to explicitly open the host if they want to allow external connections. We can add a Docker configuration section in the Vite Ruby docs (instead of my outdated example). |
Beta Was this translation helpful? Give feedback.
-
|
Hi, @ElMassimo! Thank you for all of your work on this project. I think I am encountering a similar issue, but I can't seem to figure out what I might be missing. I am also working on migrating our React/Rails app from using Webpacker to Vite. This is admittedly out of my usual wheelhouse as I haven't worked much in devops, so any help would be appreciated. I am also able to run the local Vite dev server with no issues, but I am getting a HTTP 404 error when trying to view http://127.0.0.1:3036/vite-dev/ (and there are no errors in the rails logs).
This is the link to our repo. Any help would be much appreciated! |
Beta Was this translation helpful? Give feedback.
-
|
Hi Eric! @eadams17
Unless you have an Most of the time, you wouldn't access the Vite dev server directly, and instead would visit your Rails server as usual during development. |
Beta Was this translation helpful? Give feedback.
The problem is related with a recent change in Vite, which affects systems where
localhostdefaults to::1(IPv6).Configuring
hostexplicitly to127.0.0.1should fix the problem.I will evaluate changing the default from
localhostto127.0.0.1since at the moment Vite performs that conversion and causes this issue.