Failed at first hurdle ....
This page isn’t working
xxxx.serveo.net is currently unable to handle this request.
502 error
Results 11 to 20 of 1186
-
2019-09-25, 12:32 #11
- Join Date
- Feb 2008
- Posts
- 5,504
------------------------------------------------------------------------------------
-
2019-09-25, 12:36 #12
- Join Date
- Feb 2011
- Location
- Cheshire, UK
- Posts
- 6,506
Serveo
A portscanner on 9000 wouldn’t find it.
You’d have to guess the unique part of the serveo host name and know that 443 would expose 9000 but yes it must effectively be open.
It’s the simplicity and validity of the SSL cert that makes this attractive if a little risky.
I’ll get myself an SSL cert for my router I think and use it’s in built SSL web proxyJim
https://jukeradio.double6.net
VB2.4 storage QNAP TS419p (NFS)
Living Room Joggler & Pi4/Khadas -> Onkyo TXNR686 -> Celestion F20s
Office Joggler & Pi3 -> Denon RCD N8 -> Celestion F10s
Dining Room SB Radio
Bedroom (Bedside) Pi Zero+DAC ->ToppingTP21 ->AKG Headphones
Bedroom (TV) & Bathroom SB Touch ->Denon AVR ->Mordaunt Short M10s + Kef ceiling speakers
Guest Room Joggler > Topping Amp -> Wharfedale Modus Cubes
-
2019-09-25, 12:45 #13
I agree. Serveo is the least attractive option, but I added it to the list because people have preferences for ways of doing things and it's yet another way. I have found it to be flaky as far as availability in my testing.
If I were using serveo myself, I'd always combine it with apache as an extra layer for auth. That way, serveo would handle the 'front-end' of me not having to open a port, not having to do DDNS, not get a cert. And apache would do the 'back end' of forwarding the serveo tunnel through a basic-auth capable local proxy in my network towards LMS as an extra security layer. Rather involved, but hey there's more than one road that leads to Rome.
In the end, it's only the JSON that's tracing these pathways and not audio-streams, so not a big deal to add a layer.Last edited by philchillbill; 2019-09-25 at 12:54.
-
2019-09-25, 12:53 #14
-
2019-09-25, 13:29 #15
[Announce] 'MediaServer' *certified*Alexa skill for LMS
> Serveo
> A portscanner on 9000 wouldn’t find it.
Correct: as you wouldn't get your own IP address, but only a virtual
host name, a simple IP scanner wouldn't find your LMS. A visitor would
need to know your host name. That's different from (and quite a bit more
secure than) simple port forwarding on the router, where an IP scanner
would find you.
--
Michael
-
2019-09-25, 13:45 #16
- Join Date
- Feb 2011
- Location
- Cheshire, UK
- Posts
- 6,506
I’ve realised my router also supports LetsEncrypt when coupled with DrayDDNS so I have everything I need to securely try this except an Echo Dot!!
I have Prime though so it will be here for Friday!Jim
https://jukeradio.double6.net
VB2.4 storage QNAP TS419p (NFS)
Living Room Joggler & Pi4/Khadas -> Onkyo TXNR686 -> Celestion F20s
Office Joggler & Pi3 -> Denon RCD N8 -> Celestion F10s
Dining Room SB Radio
Bedroom (Bedside) Pi Zero+DAC ->ToppingTP21 ->AKG Headphones
Bedroom (TV) & Bathroom SB Touch ->Denon AVR ->Mordaunt Short M10s + Kef ceiling speakers
Guest Room Joggler > Topping Amp -> Wharfedale Modus Cubes
-
2019-09-25, 14:57 #17
- Join Date
- Jan 2010
- Location
- Hertfordshire
- Posts
- 8,927
I installed ngrok on my Pi but when I try to run the command I get
ngrok: command not found.
What am I doing wrong?
Sent from my SM-G900F using Tapatalk
-
2019-09-25, 15:19 #18
- Join Date
- Jan 2010
- Location
- Hertfordshire
- Posts
- 8,927
-
2019-09-25, 15:37 #19
- Join Date
- Jan 2010
- Location
- Hertfordshire
- Posts
- 8,927
I succeeded in getting ngrok to run on my pi and also accessed LMS using the URL generated by ngrok via Firefox on my laptop. When I put the same URL into the skill settings adding port 443 I get "No players discovered due to connectivity error" . I am using
"https://xxxxxxxx.ngrok.io:443"
I must be making a basic error but I can't see what it is.
Sent from my SM-G900F using Tapatalk
-
2019-09-25, 15:48 #20
- Join Date
- Jan 2010
- Location
- Hertfordshire
- Posts
- 8,927