search

bfabiszewski / ulogger-server

μlogger • web viewer for tracks uploaded with μlogger mobile client
GNU General Public License v3.0
542 stars 85 forks source link

Upload tracks from mobile app leads to Bad URL error #147

Closed dancesWithCycles closed 3 years ago

dancesWithCycles commented 3 years ago

Hi, folks!

After the ulogger-server is up and running on my Debian 10 LAMP server in a local private network for testing purposes, I move forward a next step and test the track synchronization between mobile Android app and ulogger-server.

When I hit the upload button in the app, I receive Android toast messages about an error you see in the attached screenshot.

Does anyone has an idea what goes wrong?

The error messages include:

"Bad URL: no protocol: 192.168.1.181/client/index.php"

First toast: "Uploading started"

Second toast: "Uploading failed: Bad URL: no protocol: 192.168.1.181/client/index.php"

Screenshot_20201022-113638 Screenshot_20201022-113641 Screenshot_20201022-113645

Cheers!

peteman52 commented 3 years ago

That are two problems:

  1. No protocol means you have to start your URL with http(s)
  2. Technically an ip-address is no valid URL but you may try http://192.168.1.181
dancesWithCycles commented 3 years ago

Yes, indeed. That was to obvious. Of course the protocol was missing. I am so accustomed to browser that "automagically" try to add default protocols to the domain name.

Using HTTP protocol and IP address http://192.168.1.181 works. As I am running the ulogger server in a local private network I do not possess a fully qualified domain name. Using the host name of the above IP address works as well. That would look this way: http://tpt60b. Thank you very much for expanding my horizon. Cheers!