Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Loading screen fails to display #450

Open
taiwan-king opened this issue Nov 16, 2024 · 17 comments
Open

Loading screen fails to display #450

taiwan-king opened this issue Nov 16, 2024 · 17 comments
Labels
bug Something isn't working

Comments

@taiwan-king
Copy link

taiwan-king commented Nov 16, 2024

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.

@taiwan-king taiwan-king added the bug Something isn't working label Nov 16, 2024
@acouvreur
Copy link
Member

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
Copy link
Author

taiwan-king commented Nov 17, 2024

{"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
Copy link
Member

Can you give more details on the reverse proxy configuration ?

How is the sablier plugin configured ?

@taiwan-king
Copy link
Author

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
Copy link

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

@acouvreur
Copy link
Member

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
Copy link

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

@taiwan-king
Copy link
Author

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

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

您的 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
Copy link

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
Copy link

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
Copy link
Member

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

That'd be amazing, thanks

@DaveHOnCode
Copy link

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
Copy link

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
Copy link

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
Copy link

DaveHOnCode commented Dec 11, 2024 via email

@taiwan-king
Copy link
Author

taiwan-king commented Dec 12, 2024

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
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

6 participants