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

error message in piemessageosx client #16

Open
telis11 opened this issue May 6, 2016 · 7 comments
Open

error message in piemessageosx client #16

telis11 opened this issue May 6, 2016 · 7 comments

Comments

@telis11
Copy link

telis11 commented May 6, 2016

i get the error message when i try to run the OS X client
connection refused

@zanesc
Copy link

zanesc commented May 6, 2016

you need to forward port 5000 to your OS X machine through your firewall/router.

edit: you also need to forward port 4000 to your phone.

edit: the above no longer works as of commit fec3bbf. I can send messages but no longer receive them.

@atomheartbrother
Copy link

How would you go about port forwarding on your phone? Would you need to start with a static IP address?

@zanesc
Copy link

zanesc commented May 6, 2016

same process as with computer, both of these are done through the router/firewall settings. set a static IP referencing the MAC address of the device then forward ports using those static IPs.

@atomheartbrother
Copy link

Okay thank you. This might be a stupid question but.. does this only work on wifi or also mobile networks

@zanesc
Copy link

zanesc commented May 6, 2016

haha, no not stupid. I had to test it myself to see if it worked or not as well. Once you use your global IP in the setup phase it works on wifi and mobile networks. but seeing as it is still in early stages of development i have seen a few missed messages while making the switch to a different network.

@bboyairwreck
Copy link
Owner

Yeah. PieMessage was the first time working with sockets. I haven't figured out how to fail gracefully when the socket is closed. I could reconnect but honestly, Google recommends AGAINST having a socket open in the background all the time. I only wanted to use my own socket because I didn't want any messages going through any kind of Google server just for realtime notifications just for privacy/security reasons.

@spencerelliott
Copy link

spencerelliott commented Jun 8, 2016

It would be awesome if the Java server on the Mac could use Google Cloud Messaging services (https://developers.google.com/cloud-messaging/). That should be extremely reliable and doesn't require you to keep a socket open forever. Plus, it'll work on WiFi and mobile networks. All you have to do is connect to the socket when the Android app is open and pull all new messages down.

This would require a bit more setup on the user's side, but I think messages would be a lot more reliable.

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

5 participants