Could Not Connect To Server

Solar2D Win32 Desktop
#1

Hello

The school district I work for is having trouble getting logged in to the Corona Simulator on a lab of Windows 10 PCs.  When attempting to log in the users receive an error stating “Could not connect to server. Please check your internet connection.”

We do have a stable Internet connection so I’m certain that is not the issue.  However, we do use a content filter on these school devices and I’m wondering if that’s not where we’re getting hung up.  Is there any kind of whitelist available that includes the URLs needed to establish that server connection?

We are running Corona - 2018.3326

Thank you!

#2

Hi Tyler. It’s really not necessary to ask the same question to the support portal and to the forums. It just creates double work for us. The community doesn’t benefit from these questions when they are asked directly to the support channel. This should always be the first place you turn to since you get exposed to multiple people who can help you.

For the benefit of anyone following along and for search engines, here is what I replied in the support channel:

Firewalls and more often Proxies on Windows machines do tend to block access to Corona’s developer tools. 

The normal test we ask you to perform needs to be done with Internet Explorer, not edge. IE is still in Win10, but it’s hidden so you will have to search for it. When you start IE, go to this address:

https://developer.coronalabs.com/services/xmlrpc

If it works, you should get this response: XML-RPC server accepts POST requests only.

Then you should be able to use the simulator to sign in.  If not, perhaps your team that manages your content filters can get it working. 

Rob

#3

Hi Rob,

I apologize for creating extra work for you.  This is my first experience with Corona and I wasn’t aware of the preferred support sequence.  Thank you for the suggestions.

I was able to go to the address you linked within IE and received the response: XML-RPC server accepts POST requests only.  However, I’m still receiving the connection error when attempting to log in.

I have whitelisted the coronalabs.com domain in our content filter.  Unfortunately, I am not receiving any information in the reporting that indicates which specific resources are being blocked during the login attempt.  Are there any other URLs that need to be whitelisted for this connection?

Thanks again for your time.

Tyler

#4

When you say you whitelisted coronalabs.com, did you include all our subdomains like developer.coronalabs.com, portal.coronalabs.com, marketplace.coronalabs.com etc?

make sure ports 80 and 443 are open.

Rob

#5

I have added the subdomains you listed but have the same results.  Are there any additional domains that might be needed?

I can confirm that it is an issue with the content filtering.  I uninstalled the filtering agent and was able to connect.  Upon reinstalling I am no longer able to connect.  This leads me to believe there must be some other necessary domain.

Here is the output from the console after receiving the error.

15:28:37.239 
15:28:37.239  Corona Simulator 2018.3326 (Jun 25 2018 12:39:46)
15:28:37.239 
15:29:04.502  WebServices: Call system.connect failed in 1569356944 seconds: XmlRpcImplementation::execute: Could not query HTTP content length status
15:29:04.502  Request headers:
15:29:04.502 
15:29:04.502  HTTP/1.1 200 OK
15:29:04.502  Cache-Control: store, no-cache, must-revalidate
15:29:04.502  Cache-Control: post-check=0, pre-check=0
15:29:04.502  Connection: close
15:29:04.502  Content-Type: text/xml
15:29:04.502  Date: Tue, 24 Sep 2019 19:16:38 GMT
15:29:04.502  Expires: Sun, 19 Nov 1978 05:00:00 GMT
15:29:04.502  Last-Modified: Tue, 24 Sep 2019 20:29:19 GMT
15:29:04.502  Server: nginx/1.10.3
15:29:04.502  Set-Cookie: SESSc07c0747ea4ab0aa4ebc3d8416d3de7a=ae4bbad261ec7579ed7251a9ca25b834; path=/; domain=.coronalabs.com
15:29:04.502  Transfer-Encoding: chunked
15:29:04.502 
15:29:04.502       params:  {
15:29:04.502  }

#6

I dug through the code today and there is a odd reference to our old domain name:  developer.anscamobile.com

Try opening that up and let me know if that solves it.

Rob