- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 158
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
Bug: Views not incrementing for shortened URLs #659
Comments
same |
Hi, I added a try/catch in order to see the "error".. but I don't understand why execute a postFile decorator, because should only run postUrl.
The lines numbers maybe arent the same as original (because I add new code) |
don't know how no one noticed this issue for 2 years but its fixed now lol 1febd5a |
Yeah I saw the commit 5328485?diff=split&w=0 and was like "wtf... 👀" I'll check it out once the new docker image is build. Thanks @TacticalTechJay for hunting down the bug. |
yea lol the only defense I have is that I must've been tired after refactoring everything and just did something that clearly doesn't work 😭 |
What happened?
I have a zipline docker container with 3.7.11 running behind a traefik.
When I create a shortened URL and visit it I get forwarded to the target URL.
The log shows the 302 redirect properly.
zipline-1 | 2025-01-09 09:26:13,991 AM info [server::response] GET /go/test -> 302
But the views count stays at 0 no matter what I try.

I've tried incognito tabs, different browsers, curl from a different machine etc.
docker compose exec zipline yarn scripts:read-config
yields the default config for urls:
I've read the documentation but I could not find anything regarding missing setup steps or such.
Any help would be appreciated :)
Version
latest (ghcr.io/diced/zipline or ghcr.io/diced/zipline:latest)
What browser(s) are you seeing the problem on?
Firefox, Chromium-based (Chrome, Edge, Brave, Opera, mobile chrome/chromium based, etc)
Zipline Logs
Browser Logs
No response
Additional Info
The text was updated successfully, but these errors were encountered: