If I specify the port in the Server URL field, example: https://hostname:450/mobile, I get an error that the host name could not be found. So in this case where should I specify the port?
The port number should be working. We are using the non-default port number for our in-house setup too.
http://[servername]:[portnumber]/mobile can access the repository.
However, with https, the [servername] needs to be provided with the domain suffix. (even though in web browser, the doamin suffix is not required)
So, would you try to provide the full name in the server name part, and if it still can't find the host, can you try IP address in the server name part? Just want to make sure, if it's the issue of "https requires full name of the host" or it's because of the port number.
Best,
Julia
Hi, Chad,
For the hostname, have you put the domain part too? e.g. hostmachine.laserfiche.com
Or you can try to get the IP address for that part and test out if it works.
Best,
Julia
Yes, the hostname is fully qualified and it works in a browser. The issue is with adding the port, when I add the port it says the hostname can't be found so therefor it must be taking the port as literally part of the hostname.
The port number should be working. We are using the non-default port number for our in-house setup too.
http://[servername]:[portnumber]/mobile can access the repository.
However, with https, the [servername] needs to be provided with the domain suffix. (even though in web browser, the doamin suffix is not required)
So, would you try to provide the full name in the server name part, and if it still can't find the host, can you try IP address in the server name part? Just want to make sure, if it's the issue of "https requires full name of the host" or it's because of the port number.
Best,
Julia
Sorry for the confusion it was a problem with the test environment. My phone is using Verizon public DNS server and my computer is using our Internet Service Provider.
The two public DNS servers were mismatched because the change to public DNS of the customers domain was so recent.
Verizon has updated and now it is working.
Testing by IP helped me confirm this, thanks!
No problem! Glad it works. Enjoy the app! 
Best,
Julia