Loading screen fails to display

[taiwan-king]

When using traefik:v3.1.4 with sablier:v1.7.0, the loading screen displays normally. However, after upgrading to sablier:v1.8.1, the loading screen fails to display, though all functionalities still work correctly.
The refreshFrequency function also does not work correctly.

[acouvreur]

Hello @taiwan-king, can you give me more details on what you're actually seeing ?
Maybe the log details ?

What is the exact sablier image that you are using ?

[taiwan-king]

{"time":"2024-11-17T02:01:11Z","level":"info","msg":"172.19.0.4 - d53c09da6c6c [17/Nov/2024:02:01:11 +0000] \"GET /api/strategies/dynamic\" 200 6329 \"\" \"Go-http-client/1.1\" (1ms)","clientIP":"172.19.0.4","dataLength":"6329","hostname":"d53c09da6c6c","latency":"1","method":"GET","path":"/api/strategies/dynamic","referer":"","statusCode":"200","userAgent":"Go-http-client/1.1"}

sablierapp/sablier:1.8.1

https://browserquest.taiwan-homecloud.us.kg

You can give it a try,
I'm not sure if it blocks IPs from your country.

If there is, let me know your IP,
and I can help whitelist it.
When I tested, a "bad gateway" error appeared,
but refreshing the page solved it,
and I could access the website directly.
All configurations follow the official documentation.
I'm using the Ghost theme for the setup.

[acouvreur]

Can you give more details on the reverse proxy configuration ?

How is the sablier plugin configured ?

[taiwan-king]

traefik config

experimental:
plugins:
sablier:
moduleName: "github.com/sablierapp/sablier"
version: "v1.8.1"

browserquest config

http:
routers:
browserquest:
rule: "Host(browserquest.taiwan-homecloud.us.kg)"
entryPoints:
- "http"
middlewares:
- "browserquest"
service: "browserquest"
websocket:
rule: "Host(browserquest.taiwan-homecloud.us.kg)"
entryPoints:
- "websocket"
middlewares:
- "browserquest"
service: "websocket"

middlewares:
browserquest:
plugin:
sablier:
names: BrowserQuest-PHP
dynamic:
refreshFrequency: 5s
showDetails: "true"
theme: ghost
sablierUrl: http://sablier:10000
sessionDuration: 1m

services:
browserquest:
loadBalancer:
servers:
- url: "http://192.168.10.253:807"
websocket:
loadBalancer:
servers:
- url: "http://192.168.10.253:8000"

[ViktorTrojan]

Can confirm this is the case for me aswell, using nginx proxy manager

[acouvreur]

I've just tried with the latest verison and everything works on my side.

However, when there is an error in the configuration, the feedback is currently very bad.

Do you have any error on your Sablier logs ?

[ViktorTrojan]

No logs. It just does not show a loading screen, just white until it shows the webpage

[taiwan-king]

我剛剛嘗試了最新版本，一切都對我有利。

但是，當配置出現錯誤時，目前反饋非常糟糕。

您的 Sablier 紀錄上有什麼錯誤嗎？

My configuration should not have any issues,
because everything worked fine when I was using version 1.7.0.
The only thing I did was upgrade the version.
Additionally, there are no error logs displayed.

[ViktorTrojan]

Same for me, I set it up with version 1.8.1 I think and had no loading screen. Downgraded to 1.7.0 and login screen works.

I'm not sure but the redirect seems somewhat slow, it's not really slow but I would assume that there would be no noticeable delay?

[PacaAlpaca]

Also have this problem with 1.8.1
No major changes in configuration since previous version.

traefik.yml:

experimental:
  plugins:
    sablier:
      moduleName: "github.com/sablierapp/sablier"
      version: "v1.8.1"

fileConfig.yml:

http:
  routers:
    guacamole:
      entryPoints:
        - "websecure"
      rule: 'Host(`guacamole.xxx.xxx`)'
      service: guacamole
      tls: {}
      middlewares:
        - "guacamole-sablier@file"
...
  services:
    guacamole:
      loadBalancer:
        serversTransport: "xxxxx"
        servers:
          - url: "http://xxxxx:xxxx"
...
  middlewares:
    guacamole-sablier:
      plugin:
        sablier:
          group: guacamole
          dynamic:
            displayName: guacamole
            refreshFrequency: 30s
            showDetails: "true"
            theme: "shuffle"
          sablierUrl: http://sablier:10000
          sessionDuration: 20m

Before container starts (with nextcloud - 5s, with guacamole ~1min) I see cloudflare error page - "host not working" instead of sablier loading screen/theme

[acouvreur]

Is it possible for any of you to create a repository to reproduce the issue ?

That'd be amazing, thanks

[DaveHOnCode]

I even had it with the basic WhoamI example using docker as provider and Caddy as reverse proxy.

I would like to switch back to version 1.7.0, to rule out a configuration error on my side, but there is no package available for that on the docker hub. If you could provide that, I would be very thankful

[DaveHOnCode]

Could it be an issue if its only one container to start up?
At least I'm facing that issue only if I use One-Container Configurations (i. e. Stirling PDF). While using multiple container docker files, there is no issues.

Thanks for your effort!

[CarbonNeuron]

I think I figured it out. It is returning a 502 status code when the service is not up yet. And cloudflare is replacing that with a error page.

[DaveHOnCode]

No that doesn’t make sense to me. It’s just displaying a white page, without any error code and it also doesn’t reload, even then the page is finally upOn 11. Dec 2024, at 19:45, CarbonNeuron ***@***.***> wrote: I think I figured it out. It is returning a 502 status code when the service is not up yet. And cloudflare is replacing that with a error page. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

[taiwan-king]

No that doesn’t make sense to me. It’s just displaying a white page, without any error code and it also doesn’t reload, even then the page is finally upOn 11. Dec 2024, at 19:45, CarbonNeuron @.> wrote: I think I figured it out. It is returning a 502 status code when the service is not up yet. And cloudflare is replacing that with a error page. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.>

You can find the older version here: https://github.com/acouvreur/sablier.

https://hub.docker.com/r/acouvreur/sablier

[CarbonNeuron]

One person said they received a cloudflare error message. I'm getting a 502 while the service is down which cloudflare replaces.

[ardavan-ansari]

Same issue, I'm using Traefik and Cloudflare. The containers are stopped and started correctly, but the loading page is not displaying (502 error page, replaced by Cloudflare).

Downgrading to 1.7 fixes the issue.

[dbogatov]

Same. acouvreur/sablier:1.7.1-beta.1 works with the same config.

[alx-xlx]

i get the same issue, i reinserted my external ssd and saw that none of the containers are starting correctly, just showing a white screen. But now after like 2 restarts and when i check after 6hrs then everything works fine.

this is very inconsistent and unreliable software to use, there is no information on what is happening. There should be some sort of fix for this issue.

White screen isn't the best way to undrstand what has gone wrong.

[ViktorTrojan]

@alx-xlx this is open source software. A fix is mentioned, which is using an older version. If you want you can fix this issue and open a pull request, otherwise don't complain about open source software

[hitesh-singh]

Can confirm this issue still persist with Sablier v1.8.2 and Traefik v3.3.1

[Karl-V-HRR]

I have conducted some tests, and on my setup acouvreur/sablier:1.8.0-beta.8 is the last image which displays the loading screen correctly. I am using Caddy v2.9.1.

Sablier compose file

services:
  sablier:
    container_name: Sablier
    image: acouvreur/sablier:1.8.0-beta.8
    command:
      - start
      - --provider.name=docker
      - --logging.level=trace
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - ./config/sablier.yaml:/etc/sablier/sablier.yaml
    restart: unless-stopped
    labels:
      - com.centurylinklabs.watchtower.monitor-only=true
    networks:
      - Sablier
networks:
  Sablier:
    external: true

(Back instance) Caddyfile

http://jellyfin.mydomain.com {
        route / {
                sablier http://sablier:10000 {
                        group Jellyfin
                        session_duration 10m
                        dynamic {
                                display_name Jellyfin
                        }
                }
        }
        reverse_proxy   jellyfin:8096
}