[GH-ISSUE #368] The application doesn't work with IP based URL's #266

New issue

Open

opened 2026-02-28 01:23:56 +03:00 by kerem · 2 comments

kerem commented

2026-02-28 01:23:56 +03:00

Owner

Originally created by @segmentationfaulter on GitHub (Jan 24, 2016).
Original GitHub issue: https://github.com/ushahidi/SMSSync/issues/368

I was testing SMSSync and I built a web service locally which had a url http://192.168.1.4:3000/ , but SMSSync kept telling me that the endpoint is not valid. Then I deployed the same web-service on heroku and it worked. Is it a bug or what?

Originally created by @segmentationfaulter on GitHub (Jan 24, 2016). Original GitHub issue: https://github.com/ushahidi/SMSSync/issues/368 I was testing SMSSync and I built a web service locally which had a url http://192.168.1.4:3000/ , but SMSSync kept telling me that the endpoint is not valid. Then I deployed the same web-service on heroku and it worked. Is it a bug or what?

kerem commented

2026-02-28 01:23:57 +03:00

Author

Owner

@frmokoena commented on GitHub (Jan 29, 2016):

Is your phone and web service in the same network?
Also, you ought to enter the full URL including the filename. But I believe since it works on heroku it should work locally?

@frmokoena commented on GitHub (Jan 29, 2016): 1. Is your phone and web service in the same network? 2. Also, you ought to enter the full URL including the filename. But I believe since it works on heroku it should work locally?

kerem commented

2026-02-28 01:23:57 +03:00

Author

Owner

@segmentationfaulter commented on GitHub (Jan 30, 2016):

Yes, phone and web-service were on the same network. EnvayaSMS worked with the same IP based URL but SMSSync did not.

@segmentationfaulter commented on GitHub (Jan 30, 2016): Yes, phone and web-service were on the same network. EnvayaSMS worked with the same IP based URL but SMSSync did not.