[bug] can't connect to tauri.localhost

[danitor1]

Hi guys. I copy and paste a question made in other web because I have exactly the same problem and I need help:

Using angular when opening a router link on the build version always gives a
"This site can’t be reached; tauri.localhost refused to connect";
This does not happen on the dev version due to the fact that the dev version is not running on tauri.localhost but on http://localhost:4200/.

In order for a route link to work on angular every link must lead back to index.html. I assume this works on the dev version since it receives information from the local webpack server. However, on the build version when a new window opens there is no information being sent so the routes always fail to complete. This happens on something as simple as a or even left click open link on a new window.

I don't understand what the issue could be or if there is a way to resolve it so that on the installed version these new windows actually complete.

Can you explain the solution? Thanks a lot.

[danitor1]

THE ANSWER:
This happens when you install Tauri on an Angular project. You have to change the "distPath" from "../dist" to "../dist/nameOfYourProject" and the .exe will work perfectly.

[mota57]

no, issue persist.

[ZeeshanAhmadKhalil]

same issue for me looks like its not picking up the out/dist folder

[ZeeshanAhmadKhalil]

In my case issue was on the next.js side. I was not creating the pages/index.html file which becomes the entry file index.html after next build && next export.

Due to this reason was getting a white screen. After adding pages/index.html and redirecting to my main app, the issue got resolved.

[Tenkaklet]

Thanks mate! This made rush outta bed a continue coding! 🥇

[lucasmolinari]

This happens when you install Tauri on an Angular project. You have to change the "distPath" from "../dist" to "../dist/nameOfYourProject" and the .exe will work perfectly.

You actually need to point to the browser folder too if that is the case. The full path should be: ../dist/[ProjectName]/browser

[TheRedSpy15]

Anyone else having this issue with sveltekit?

[FabianLars]

Are you using the static-adapter? It's required to make sveltekit work in Tauri (and similar GUI frameworks).

We also give a short intro on that in our guide https://tauri.app/v1/guides/getting-started/setup/sveltekit#sveltekit-in-ssg-mode

[TheRedSpy15]

Yah I'm using the static-adapter, and added a fallback (index.html) for SPA

It works when I run npm run tauri dev but building with npm run tauri build and running the exe it just opens a window says it can't connect to tauri.localhost

[TheRedSpy15]

I'm suspecting it's caused by my project's reliance on SSR. I found a google result for your comment here: #2751 (comment) in hopes of maybe bundling the server code. But it seems I would have to rewrite my +page.server.ts code to rust, which is kinda a no go for the amount I would need to do

but the links there both lead to 404 pages

I'm gonna put my plans for using Tauri on hiatus for now. But am I curious as to why is works flawlessly with run dev while building an executable leads to bad results

[FabianLars]

I'm gonna put my plans for using Tauri on hiatus for now. But am I curious as to why is works flawlessly with run dev while building an executable leads to bad results

Because dev mode uses sveltekit's dev server while build mode doesn't have a server so only code that's fully SPA/SSG compatible can work.
That's one of the reasons i rarely recommend sveltekit for tauri apps (or similar gui frameworks). The difference between dev and build is just too big imho and it's often not exactly obvious what won't work in build mode.

This is the new link for the 404 page btw: https://tauri.app/v1/guides/building/sidecar

[CptLando]

Anyone else having this issue with react native / expo?

[Yu15693]

It seems that Tauri only looks for index.html in the root path of distDir.
Therefore, check your dist directory to see whether the index.html is in the correct location.