Error loading WebAPP

Targets Web
1

Hello,
I have webapp on ubuntu server.
When i upgrade my webapp from xojo 2016 to xojo 2017r2.1 or later, my app works well with an url with the server IP (http://37.187.78.29/cgi-bin/cimserv/cimserv.cgi)

but not with virtual host (https://drucourt-amethyste.collectivites.net/)

error message id :
Failed to load resource: net::ERR_NAME_NOT_RESOLVED
OR
GET https://framework/favicon.ico net::ERR_NAME_NOT_RESOLVED ON framework/favicon.ico

Can you help me ?
Thanks

2

Have you set permission on the app/resources to 0755 and uploaded all folders and resources used by you app?

Does your web host support XOJO web apps?

Visiting the web link provided does nothing here.

3

I have 0755 permissions on ressources folder.
I have some webapp in xojo 2016 that run smoothly.

I can see errors with F12 key.

4

I would suggest to first configure your virtual host just for the IP, and make sure you can visit your site as:
https://drucourt-amethyste.collectivites.net/cgi-bin/cimserv/cimserv.cgi

Then you can try to configure to work without the cgi-bin part.

Or maybe there is a change in Xojo and now it has a different way to resolve the execution directory

Edit: the URL I posted here was entered manually, just tested on a browser and it works.

5

Hello,
With https://drucourt-amethyste.collectivites.net/cgi-bin/cimserv/cimserv.cgi, its OK.
We have found on xojo release note 2017r2 : CGI Web Applications now only listen on the localhost interface.
What does it change on apache configuration ?
thanks

6

[quote=411327:@Laurent MIQUEL]Hello,
With https://drucourt-amethyste.collectivites.net/cgi-bin/cimserv/cimserv.cgi, its OK.
We have found on xojo release note 2017r2 : CGI Web Applications now only listen on the localhost interface.
What does it change on apache configuration ?
thanks[/quote]
Nothing. All this means is that the app only binds the local port number. So for instance, if the cgi script chose port 53752, prior to 2017r2 it would listen on local host and any public or private up addresses even though it should never have been getting requests from there.

7

Make sure your virtual host maps its changes in both directions. That is, if you’re mapping a domain name to a full url on the incoming data, you must also map the full url to the domain name on the outgoing data.