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

Service gone after network error #5

Open
magnuswikhog opened this issue Jan 10, 2020 · 3 comments
Open

Service gone after network error #5

magnuswikhog opened this issue Jan 10, 2020 · 3 comments

Comments

@magnuswikhog
Copy link

I installed ngrok and got it working on a Raspberry Pi using this library, but unfortunately it seems that if the network connection goes down for a few hours and then comes back, ngrok will not reconnect. If I run service --status-all I don't see the ngrok service.

@peter279k
Copy link
Contributor

I think this issue is about ngrok.service file setting.

After looking at the After=network.target setting on [Unit] block, it has been consider using the network-online.target instead.

These are different and some descriptions are as follows:

On current systems, ordering after network.target just guarantees that the network service has been started, not that there's some actual configuration. You need to order after network-online.target and pull it in to achieve that.

Some useful references are as follows:

@suan
Copy link

suan commented Feb 15, 2021

@magnuswikhog @peter279k Curious, is this still an issue, and has it been verified that using network-online.target instead of network.target fixes it?

@peter279k
Copy link
Contributor

peter279k commented Feb 16, 2021

Yes. You can refer my posts I provide :).

I use the network-online for my Ngrok with systemd and it's worked when having the network error.

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