# Screenly with LTE Stick

**URL:** <https://forums.screenly.io/t/screenly-with-lte-stick/380>\
**Category:** Anthias\
**Created:** [September 21, 2020, 8:32am UTC](https://forums.screenly.io/t/screenly-with-lte-stick/380 "2020-09-21T08:32:53Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![wusel](https://avatars.discourse-cdn.com/v4/letter/w/f14d63/32.png) [@wusel](https://forums.screenly.io/u/wusel)\
**Post date:** [September 21, 2020, 8:32am UTC](https://forums.screenly.io/t/screenly-with-lte-stick/380/1 "2020-09-21T08:32:53Z")

</div>

Hey,  
I managed to get the Raspberry with a working internet connection but Screeny thinks there is no internet connection and just shows the WiFi Hotspot page. I installed a ddns tool to and connected it with an [noip.com](http://noip.com) account which get the current external IP from the LTE-Stick. But i cant communicate with it from outside. Anyone tried someting similar and got it to work?

---

<div class="post-metadata">

**Author:** ![luisscreenly](https://avatars.discourse-cdn.com/v4/letter/l/90ced4/32.png) [@luisscreenly](https://forums.screenly.io/u/luisscreenly)\
**Post date:** [September 27, 2020, 1:06pm UTC](https://forums.screenly.io/t/screenly-with-lte-stick/380/2 "2020-09-27T13:06:53Z")

</div>

I can’t speak to why screenly thinks there is no internet connection, but have you verified you are able to reach outside with the pi?

As for communicating to your pi from the outside, did you establish port forwarding rule on your router?

---

<div class="post-metadata">

**Author:** ![wusel](https://avatars.discourse-cdn.com/v4/letter/w/f14d63/32.png) [@wusel](https://forums.screenly.io/u/wusel)\
**Post date:** [September 28, 2020, 12:00pm UTC](https://forums.screenly.io/t/screenly-with-lte-stick/380/3 "2020-09-28T12:00:29Z")

</div>

I found an other APN that give the stick not a Telekom private IP but a real external IP, now if i type in these i can see the balena screen for connecting to a WiFi. But why? i allready have Internet access. So now i just need to get the ddns to work and screenly.

Edit: if i connect the pi with a cable, and pull it out than everything works, so all i have to do is to, idk let it think there is a connection?

Edit 2: I think Screenly is looking vor an active connection from wlan0 or eth0, so if there is ppp0 interface withi an active connection, Sceenly doesnt know it and doesnt check it. So i think i need to find where Screenly checks eth0 oder wlan0 if up an maybe add the ppp0 interface.

---

<div class="post-metadata">

**Author:** ![wusel](https://avatars.discourse-cdn.com/v4/letter/w/f14d63/32.png) [@wusel](https://forums.screenly.io/u/wusel)\
**Post date:** [September 29, 2020, 1:43pm UTC](https://forums.screenly.io/t/screenly-with-lte-stick/380/4 "2020-09-29T13:43:27Z")

</div>

Edit 3: Well i comment out the line

`if __name__ == " __main__":`

just for fun and rebooted the pi. Now it shows a screen saying something like, cant resolve ip address, and after a minute it shows the assets and it works.  
And in /etc/nginx/sites-enabled/screenly.conf i changed the upstream wifi-connect IP from

`server 192.168.42.1:9090`  
to  
`server 127.0.0.1:8080`

I don’t know what and why I did that, but in the end it kind of works how i want soo… 😄