search

ASCOMInitiative / ASCOMRemote

The ASCOM REST based Remote Driver Server and Remote Access Clients
GNU General Public License v3.0
57 stars 15 forks source link

Exception while attempting to start the API discovery listeners #37

Closed michealroberts closed 2 years ago

michealroberts commented 2 years ago

So, I have a Alpaca ASCOM API remote server set up on a VM machine on Azure*, at the port 8010 (*for testing purposes)

However, for some reason, the connection hangs and is unable to respond.

Within the Windows Server VM, if I open any browser, and say navigate to: http://127.0.0.1:8010/api/v1/telescope/0/altitude I see the following response:

{"Value":38.92139,"ClientTransactionID":0,"ServerTransactionID":11,"ErrorNumber":0,"ErrorMessage":"","DriverException":null}

So I can confirm that it seems to be working, and working as intended.

I have also whitelisted inbound connections to 8010 within the VM, using Windows Firewall rules, and I have also added an inbound port rule to the network handling, but there still is the infinite hang.

There is certainly something I have done wrong in configuring the server, perhaps something to do with this:

Screenshot 2022-08-15 at 14 22 18

However, when I add the IP address of the public IP address for the VM, I see the following issue:

Screenshot 2022-08-15 at 14 26 05

So, it can't seem to discover ...

Would anyone be able to work with me to understand how to setup on a VM?

michealroberts commented 2 years ago

Ooof, always the way, as soon as you try something it works! Haha

So it seems that if you set it to an IP address you need to stop and the start the server again... D'oh!

Peter-Simpson commented 2 years ago

Hi Michael, glad you have it sorted!

Best wishes, Peter