Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
I have helped myself.Who knows some soul appears here with a clue to get this situation fixed. Just thank you for now.
Shlink shortener?Hi Everyone,
Shlink is working fine since its installation, but now after a couple of months it is returning an error (below). Couldn't anyone please help me with some clues how to solve this issue?
Thanks in advance.
View attachment 2906
Hi Rusty,Shlink shortener?
Running via reverse proxy? Port traffic is not the problem. Looks like the service is not running or the reverse proxy is not reversing to the right port.
Any recent changes? Is this running in docker?
So on mobile while you are in your LAN or outside? Not sure what URL in shlink will give you that .../sharing URL. Is that something custom you did? Tag, or slug?Hi Rusty,
No changes at all, running in docker. Reverse proxy yes.
Just found out what the problem was, I run it on my smartphone under VPN connection! Can't deal with it :-/
I create another shortlink just for ongoing testing purpose, both links loading from desktop and mobile WiFi on the same network. On PC works great as always.
But mobile when I turned vpn off, returns me another error:
This connection isn't private
View attachment 2907
Not just shlink but also host site giving me this time "err:connection refused" warning.
On same network via wlan, I just tried now, however, no errors this time, the link goes to gofile.me for while then goes to "local ip:port/sharing/logn_URL_trail_code" when in fact it was supposed to show "mydomain:port/sharing/long_URL_trail_code".So on mobile while you are in your LAN or outside? Not sure what URL in shlink will give you that .../sharing URL. Is that something custom you did? Tag, or slug?
In any case, two separate errors in this thread.
Long URL: http://gofile.me/4gzT9/2NenUczEm
Short URL: http://s1.bjsa.cc/dummyfile
Well, yes I did.Did you install Web Station recently?
Yes, I'll do it. Meanwhile I took a look at this configuration, just don't know what the difference ist between nginx and apache.Not sure how things are configured on your NAS/network, so it’s a shot in the dark.
Can you stop the Web Station package and see if everything works as it should with the above?
Sorry, but not just to stop web station ist enough. I had to uninstall http service 2.4 and 2.2, and other packs that depends on, like these:I don’t know what are you trying to do!
Why don’t we try fixing the problem you posted about above first.
Just to be clear. All you need to do for testing is to go:
Web Station > drop down menu and choose stop.
See if that makes any difference (for the links).
Why do you need Shlink to connect devices internally?except for shlink links which still remains dead, i.e. whether device connected via lan, wlan or 4g).
That's mistake, not links as connections I meant links as "short url" which in essence is also a link.Can you recall if it all started after you installed Web Station?
Keep in mind that enabling Web Station claims ports 80 and 443.
Why do you need Shlink to connect devices internally?
That's the purpose of shorting a link when the original link is too long to paste, for example, onto a mobile instant message.I understand what you meant. The question still stands, why do you need to shorten the links?
You’re introducing an extra layer where things can go wrong and cause problems (as the case now).
Why not use direct links?
(1) | Chrome | OK |
Firefox | OK | |
Brave | This site can't be reached - refused to connect - ERR_CONNECTION_REFUSED | |
(2) | Chrome | This site can't be reached - refused to connect - ERR_CONNECTION_REFUSED |
DuckDuck | Website unavailable - refused to connect - ERR_CONNECTION_REFUSED | |
Brave | This site can't be reached - refused to connect - ERR_CONNECTION_REFUSED | |
(3) | Chrome | This site can't be reached - refused to connect - ERR_CONNECTION_REFUSED |
Firefox | Unable to connect - can't establish a connection to server | |
Brave | This site can't be reached - refused to connect - ERR_CONNECTION_REFUSED | |
(4) | Chrome | Brings up a Synology Page "Sorry, the page you're looking for was not found" |
Firefox | Brings up a Synology Page "Sorry, the page you're looking for was not found" | |
Brave | Brings up a Synology Page "Sorry, the page you're looking for was not found" | |
(5) | Chrome | Leads to a long url page but stops pointing to local ip and port/sharing/long_url_code by giving a warning "your connection is not private" ERR_CERT_COMMON_NAME_INVALID |
DuckDuck | OK | |
Brave | Leads to a long url page but stops pointing to local ip and port/sharing/long_url_code, however shows up page giving the oportunity to dowload the file |
Who knows some soul appears here with a clue to get this situation fixed. Just thank you for now.Maybe I misunderstood your use. I thought, from your posts above, that you’re using shortened links for your devices on the LAN to provide access to the NAS (e.g. laptop and camera), in addition to shares that you send outside.
That’s what I meant when I asked why.
If I were you, I’d focus on fixing direct (non-shortened) access first and then turn to Shlink. Start internally (LAN) and work your way out to the WAN (remote access).
I have helped myself.Who knows some soul appears here with a clue to get this situation fixed. Just thank you for now.
We use essential cookies to make this site work, and optional cookies to enhance your experience.