You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just implemented Shlink on Openshift with a MSSQL DB.
It works fine, but sometimes i get the error that creating new Shortlinks with a tag attached runs into a timeout.
Thats the same with problem when using the Web Client or using the API, i always get an error.
The interessing point is, that it works very well when i add another tag, and in past it also worked with the tag "inf"
Now i get as Response on a POST with the word "inf" in the tags:
504 Gateway Time-out
The server didn't respond in time.
How can i start a debug on the docker container? The standard Log doesn´t output anything during this error...
Expected behavior
Minimum steps to reproduce
The text was updated successfully, but these errors were encountered:
It’s interesting that it’s possible to first create a link in the usual way, and then, in a second step, add a tag to the previously created link. This also works without any issues with the tag — in my case, inf. This could be a possible workaround. However, the question remains why, in some cases, certain tags don’t work right away when the link is created.
Shlink version
4.4.6
PHP version
docker image
How do you serve Shlink
Docker image
Database engine
MicrosoftSQL
Database version
Current behavior
Just implemented Shlink on Openshift with a MSSQL DB.
It works fine, but sometimes i get the error that creating new Shortlinks with a tag attached runs into a timeout.
Thats the same with problem when using the Web Client or using the API, i always get an error.
The interessing point is, that it works very well when i add another tag, and in past it also worked with the tag "inf"
Now i get as Response on a POST with the word "inf" in the tags:
504 Gateway Time-out
The server didn't respond in time.How can i start a debug on the docker container? The standard Log doesn´t output anything during this error...
Expected behavior
Minimum steps to reproduce
The text was updated successfully, but these errors were encountered: