[Bug]: Standard Laravel install with Vite - CSS not loading

[sitesurfer]

[Bug]: Standard Laravel install with Vite - CSS not loading

[regorlladu]

Having the exact same issue, i paid for pro and atm im stuck at getting this work as described. I look forward to using this tool during my development projects

[sitesurfer]

Any response on this please? I have emailed you as well, naturally paying for a pro upgrade and things not working as advertised is not ideal.

[Ssionn]

Have you tried

npm run dev

or

npm run build

You have to run them with expose.

[prof-anderson-trindade]

Any response on this please? I have emailed you as well, naturally paying for a pro upgrade and things not working as advertised is not ideal.

@sitesurfer

Have you tried force https in AppServiceProvider?

public function boot(): void { URL::forceScheme('https'); }

[hichemnightowl]

try npm run dev --host after that you can run expose

[henningd]

I tested it too. Locally all works fine. When I test it with my mobile phone, the site will be shown, but without all tailwind design. Only local css is working.

[eiiot]

+1, would like to be able to use this with my phone if possible

[yehuuu6]

Did anyone actually solve this?

[regorlladu]

Did anyone actually solve this?

This css issue is caused by having the 'npm run dev' running stop your local server, and then share with expose, it will then work.

[yehuuu6]

Did anyone actually solve this?

This css issue is caused by having the 'npm run dev' running stop your local server, and then share with expose, it will then work.

The page at 'https://ncgak7qxy6.sharedwithexpose.com/' was loaded over HTTPS, but requested an insecure stylesheet 'http://ncgak7qxy6.sharedwithexpose.com/build/assets/app-Brkf_2h0.css'. This request has been blocked; the content must be served over HTTPS.

I get this error can you help me with this? The page tries to load every asset using http. images, css bundles, etc.

[yehuuu6]

<meta http-equiv="Content-Security-Policy" content="upgrade-insecure-requests">

Adding this to meta tag fixed the issue but it is not recommended I guess.