Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Raspberry Pi shuts down when accessing craft beer pi home page via port forwarding #265

Open
Steven-Gassert opened this issue Aug 16, 2021 · 5 comments

Comments

@Steven-Gassert
Copy link

Steven-Gassert commented Aug 16, 2021

Description

Perhaps this is a raspberry pi security feature, but whenever I access the crafbeerpi UI on localhost via port forwarding from an outside network, my raspberry pi immediately crashes. Was curious if anyone would be able to provide an explanation for this behavior or provide some setups they have used to access craftbeerpi from outside the network it is connected to.

Flow with Nginx

Outside network --> My wifi router port forwarding to raspberry pi --> nginx running on raspberry pi --> craftbeer pi running on localhost

I've also seen this behavior when using ngrok to forward requests to the craftbeer pi server running on localhost

Flow with Ngrok

Outside network --> ngrok --> craftbeerpi running on localhost

@lalo-uy
Copy link

lalo-uy commented Aug 16, 2021 via email

@Steven-Gassert
Copy link
Author

@lalo-uy My idea was that I would be able to forward requests to several applications running on my local network.

In the past I've also seen this behavior while port forwarding via ngrok

Similar flow

Outside network --> ngrok --> craftbeerpi running on localhost

I'll update the description with this additional info

@lalo-uy
Copy link

lalo-uy commented Aug 18, 2021 via email

@Lagerman
Copy link

Lagerman commented Aug 18, 2021 via email

@Steven-Gassert
Copy link
Author

Thanks for the replies guys. I do currently use VNC when connecting to my pi.

My original idea was that I would be able to share a URL with non technically savvy family members who would be able to access the craft beerpi UI remotely (perhaps behind an authentication prompt) hence the preference to avoid some of the existing solutions.

The really strange part is that when I do finally make a connection to the local host via the networking paths above, the entire pi shuts down and I am no longer able to access it via ssh or vnc. That’s why my original thought was that perhaps this was some sort of security feature to prevent outside traffic from gaining control of gpio pins ect

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants