Using Octane in Laravel Livewire SPA (production)

[MinKhantNaung]

Octane Version

2.9

Laravel Version

12.9

PHP Version

8.3

What server type are you using?

FrankenPHP

Server Version

I don't know because I uninstalled Octane from my production server.

Database Driver & Version

No response

Description

I tried running Octane using FrankenPHP in my Laravel Livewire (SPA) production setup. I'm using Supervisor to manage the Octane process with the following command:

php artisan octane:frankenphp --port=8000

Octane starts successfully, and the site works as expected — including route switching via Livewire SPA.

However, when I reload the page, the CSS styles are not loading in production. Everything else seems to work fine.

Does anyone know why this might be happening or how to fix it?

Thanks in advance!

Steps To Reproduce

Set up a Laravel Livewire SPA project.

Install and configure Laravel Octane with FrankenPHP.

Run Octane using:

php artisan octane:frankenphp --port=8000

Use Supervisor to keep the process running in production.

Visit the site in the browser — it loads and works fine.

Switch between routes — everything works as expected.

Refresh/reload the browser.

CSS styles are no longer applied.

[AlliBalliBaba]

How are you loading your CSS styles? Is it vite locally and just static files in production, where are you loading the static files from?

What are you seeing in your browser's network tab when loading the css files? Hard to guess what's going wrong based on your desrciption

[MinKhantNaung]

When accessing the main page at https://animefeverzone.com, all assets (like app-Cj0oFeuw.js and related CSS files) load correctly.
However, when I reload a sub-page such as https://animefeverzone.com/topic/anime, the JS and CSS assets are blocked by the browser with a (blocked: mixed-content) error in the network tab.

I fixed the issue by adding this code in AppServiceProvider.php:
public function boot() { if (app()->environment('production')) { URL::forceScheme('https'); } }

Then I cleared and cached the config, and restarted Octane.
Is forcing HTTPS in AppServiceProvider the best practice for handling this situation in production with Octane?
Or is there a better/more recommended way?

[AlliBalliBaba]

A yeah I think that is a common issue when you are behind a reverse proxy and Caddy does not detect that the request actually comes via https. I think this can also be solved by whitelisting the correct proxy IPs, but the easier option is to just do what you did and force Laravel to always create HTTPS links. I think this also should be possible via the octane.php config by setting the environment variable OCTANE_HTTPS=true (haven't tried that though)

[MinKhantNaung]

Yes, I also tried setting OCTANE_HTTPS=true before forcing HTTPS in the AppServiceProvider.

However, after setting OCTANE_HTTPS=true, when I ran sudo nginx -t, I encountered an SSL-related error.
My server uses Certbot for SSL certificates, and it seemed like the Octane HTTPS handling conflicted somehow with the existing Nginx + Certbot SSL setup.

[Alhiane]

i was having issue with my filament on spa mode, it didn't work
and all idid is add OCTANE_HTTPS=true

[AlliBalliBaba]

Another way of forcing https would be by adding it explicitly to the php_server or php env in the Caddyfile (don't do this with http locally though):

php_server {
        ...
	env HTTPS on
}

Otherwise using URL::forceScheme('https') is probably more consistent than OCTANE_HTTPS

[MinKhantNaung]

Yes, I set OCTANE_HTTPS = true and it works well now.