Synology web server - site loads, nothing works, blinking eye icon about flox HOT 4 CLOSED

Hi,

Sorry for the useless post but I wish flox was "more" maintained and supported as easy packages to install on NAS. That would be great to replace trakt.tv. It is already for me pretty much difficult to run on a linux machine (Fedora 33).
@AlexFullmoon, have you managed to make it work on your NAS?

Regards,

from flox.

Actually, yes. I run it in Docker, using theryecatcher/flox fork, and building docker image locally — there might be some other changes in that fork.

The fix is forcing https on things that might try loading via http. Mainly scripts. I still sometimes get broken images though.

diff --git a/backend/app/Providers/AppServiceProvider.php b/backend/app/Providers/AppServiceProvider.php
index 35471f6..31813e6 100644
--- a/backend/app/Providers/AppServiceProvider.php
+++ b/backend/app/Providers/AppServiceProvider.php
@@ -3,6 +3,7 @@
 namespace App\Providers;
 
 use Illuminate\Support\ServiceProvider;
+use Illuminate\Support\Facades\URL;
 
 class AppServiceProvider extends ServiceProvider
 {
@@ -13,7 +14,8 @@ class AppServiceProvider extends ServiceProvider
      */
     public function boot()
     {
-        //
+       $this->app['request']->server->set('HTTPS', true);
+       URL::forceScheme('https');
     }
 
     /**
@@ -23,6 +25,8 @@ class AppServiceProvider extends ServiceProvider
      */
     public function register()
     {
-        //
+        if (env('APP_ENV') === 'production') {
+           $this->app['request']->server->set('HTTPS', true);
+        }
     }
 }

diff --git a/public/.htaccess b/public/.htaccess
index 903f639..9ccd6c9 100644
--- a/public/.htaccess
+++ b/public/.htaccess
@@ -4,6 +4,10 @@
     </IfModule>
 
     RewriteEngine On
+	RewriteCond %{HTTPS} !=on
+    RewriteCond %{HTTP:X-Forwarded-Proto} .
+    RewriteCond %{HTTP:X-Forwarded-Proto} !https
+    RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
 
     # Redirect Trailing Slashes If Not A Folder...
     RewriteCond %{REQUEST_FILENAME} !-d

from flox.

Actually, yes. I run it in Docker, using theryecatcher/flox fork, and building docker image locally — there might be some other changes in that fork.

The fix is forcing https on things that might try loading via http. Mainly scripts. I still sometimes get broken images though.

diff --git a/backend/app/Providers/AppServiceProvider.php b/backend/app/Providers/AppServiceProvider.php
index 35471f6..31813e6 100644
--- a/backend/app/Providers/AppServiceProvider.php
+++ b/backend/app/Providers/AppServiceProvider.php
@@ -3,6 +3,7 @@
 namespace App\Providers;
 
 use Illuminate\Support\ServiceProvider;
+use Illuminate\Support\Facades\URL;
 
 class AppServiceProvider extends ServiceProvider
 {
@@ -13,7 +14,8 @@ class AppServiceProvider extends ServiceProvider
      */
     public function boot()
     {
-        //
+       $this->app['request']->server->set('HTTPS', true);
+       URL::forceScheme('https');
     }
 
     /**
@@ -23,6 +25,8 @@ class AppServiceProvider extends ServiceProvider
      */
     public function register()
     {
-        //
+        if (env('APP_ENV') === 'production') {
+           $this->app['request']->server->set('HTTPS', true);
+        }
     }
 }

diff --git a/public/.htaccess b/public/.htaccess
index 903f639..9ccd6c9 100644
--- a/public/.htaccess
+++ b/public/.htaccess
@@ -4,6 +4,10 @@
     </IfModule>
 
     RewriteEngine On
+	RewriteCond %{HTTPS} !=on
+    RewriteCond %{HTTP:X-Forwarded-Proto} .
+    RewriteCond %{HTTP:X-Forwarded-Proto} !https
+    RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
 
     # Redirect Trailing Slashes If Not A Folder...
     RewriteCond %{REQUEST_FILENAME} !-d

That seems already good. Yet Docker seems far beyond my skills. Can't go even past the ./env setup.

Hope someone will take over flox development. Anyway thanks for your answer!

from flox.

Hey, sorry for the late response. I will be completely redeveloping Flox and will add Docker support. So that such issues should hopefully not occur.

from flox.