-
-
Notifications
You must be signed in to change notification settings - Fork 264
[BUG] 400 Bad Request with latest version of shlink docker container #379
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
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
I have the same problem on swag without services (standalone container):
Log:
|
@flurmind you have two different issues unrelated to the topic of this issue. The @gabriel-lando also has one of the issues.
@gabriel-lando looking at shlinkio/shlink#1796 the dev replied that they had no issue using a vanilla nginx container with a similar config, but one specific line is missing in their config because it's specific to swag: include /config/nginx/proxy.conf; Could you try removing that line from your shlink proxy? I don't think that should be considered the final fix, but if I'm correct it could lead us to a more correct solution. |
Hi @nemchik thanks for your help :) You are right, I commented out this Update: Update 2: Update 3: |
I would be fine with shipping a config in swag that uses https://github.com/linuxserver/reverse-proxy-confs/blob/master/_template.subdomain.conf.sample as the template (basically just follow the instructions in the file comments). I don't think any of the extra |
Is there an existing issue for this?
Current Behavior
After updating
shlink
to latest version, which changed the default runtime to Roadrunner, it stopped working when trying to access viaswag + nginx
. If I try to access it directly (usinghttp://container-ip:8080/short-url
it works.I started a thread at the shlink GH, but what we found is that it seems to be an issue with some swag/nginx configuration (shlinkio/shlink#1796).
I tried to enable "debug" logs on the
nginx.conf
file, but nothing is being logged.If I try to deploy a default
nginx
container, pointing toshlink
, it works.Obs: if use an older tag of the
shlink
docker image or the current version, but with theopenswoole
runtime (likeshlinkio/shlink:stable-openswoole
, it works. The latest version (3.6.0) changes the runtime toRoadrunner
, what seems to be the cause of the issue with swag.Expected Behavior
No response
Steps To Reproduce
docker-compose.yaml
file (content in theDocker creation
section)..env
file (content in theDocker creation
section).swag
data directory.shlink
, add the configuration file in/data/swag/nginx/proxy-confs/url.subdomain.conf
(content in theDocker creation
section).https://url.example.com
, it should redirect tohttps://app.shlink.io/
if working, but instead it is showing a400 Bad Request
message. But if you accesshttp://shlink-vm-ip:8080
, it redirects you to the right URL.Environment
CPU architecture
x86-64
Docker creation
docker-compose.yaml
:.env
file (replacing example.com by a valid domain)nginx
configuration file (url.subdomain.conf
)Container logs
The text was updated successfully, but these errors were encountered: