"Oops! Could not connect to this Shlink server" when adding a server at https://app.shlink.io #1811
-
This interface has 3 input fields
Currently I have got shlink server installed at my server. sudo -u www-data php7.4 /var/www/html/shlink/bin/cli short-url:list sudo -u www-data php7.4 /var/www/html/shlink/bin/cli short-url:generate they are working fine. I tried typing in Short URL generated at the browser, Not sure how to setup the shlink Client at https://app.shlink.io/ I tried to enter the 3 input fields value as follow name : shlink But I keep getting an error How do proper setup of shlink client so that it can interact with shlink server endpoint? Thank you |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
There's a couple of things you can check. First of all, Shlink has not supported PHP 7.4 for quite some time. The minimum supported version in current stable Shlink is PHP 8.1, but next version will only support 8.2, so I would recommend updating to that version. Then, you won't be able to connect to a Shlink server that is not served with HTTPS while using https://app.shlink.io, which is served with HTTPS, because of content restrictions in the browser (if the http was just an example, then ignore this point). And finally, please check the server response from the browser network tab to see the actual error, and the logs generated by Shlink. Those two should throw some light on the root cause. |
Beta Was this translation helpful? Give feedback.
There's a couple of things you can check.
First of all, Shlink has not supported PHP 7.4 for quite some time. The minimum supported version in current stable Shlink is PHP 8.1, but next version will only support 8.2, so I would recommend updating to that version.
Then, you won't be able to connect to a Shlink server that is not served with HTTPS while using https://app.shlink.io, which is served with HTTPS, because of content restrictions in the browser (if the http was just an example, then ignore this point).
And finally, please check the server response from the browser network tab to see the actual error, and the logs generated by Shlink. Those two should throw some light on the root …