![]() Use the Enable remote Indigo client access checkbox to allow remote Indigo Clients on other Macs to connect to the Indigo Server. This is more secure since you can revoke a key if it gets compromised without having to change passwords in wherever you may need to use them. It also will allow REST API calls to use an API key for authentication rather than a username/password. Use the Enable OAuth and API Key authentication checkbox to enable 3rd party services like Alexa. Reflectors are included as part of your Up-to-Date subscription. This option requires a you to have configured a Reflector, which handles maintaining the secure connection to Indigo Server automatically. Use the Enable secure internet access via Indigo Reflector checkbox for secure Web browser access from anywhere. Use the Override Web server (HTTP) port number: checkbox to change the TCP/IP port number that the web server uses to serve content and browsers will use to browse the web control pages. Older services may require this, though we recommend against using it. This setting allows you to insert the username/password in the URL line. Use the Also allow HTTP Basic authentication (less secure) checkbox to enable HTTP Basic authentication. You must enter a username and password if you enable remote access. Use the Allow remote access checkbox to enable remote access from other Macs and Web browsers. This option will also make sure the Indigo Server process is automatically relaunched if it crashes. ![]() Use the Auto start Indigo Server on user login checkbox to have the Indigo Server automatically launched whenever your current OS X administrator user account is logged in. This will also start the built-in Web server, allowing remote access from Web browsers on other computers and remote access from iPhones and iPod Touches. This will allow the server to run in the background on your Mac with no visible UI, even when the Indigo Client is not running. To recover, just recover that directory and then run the Indigo 2022.1 installer again (which will repair any permission issues that Time Machine may have introduced).Ĭhoose the Standard Indigo Startup radio button to start the Indigo Server process independently of the Indigo Client. You can tell the location of your database file by Command-clicking the database name in the title bar of the Home Window. If that's the case you'll need to make sure that you've backed it up as well. Another thing to note is that it's possible that you've stored your database in a non-standard location, like for instance the Documents folder in the home folder for the account under which Indigo is installed. Use the Go→Go to Folder… menu item in the Finder and paste in the path above to get there easily). Note: this is the Library folder at the top level of your hard drive, not the one in your User folder. Library/Application Support/Perceptive Automation/ Backing up your Indigo installation is very simple: just make sure that your backup program is backing up this folder: ![]() Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread. download star catalog) and Gatekeeper settings for Stellarium. Could you check network access operating from Stellarium (e.g. This is very bad and seems like Stellarium cannot connect to network. Satellite has invalid orbit: "OSIRIS-3U" "43027"Įrror: unable to find Telescopeor EQUATORIAL_EOD_COORD property. will not start again current update is complete. Download error: While trying to access " " the following error occured: "Connection timed out" If you need anything more from me let me know (however that works)Įxoplanets] Already updating. INDIGO server is on a Raspberry Pi with up to date os (Buster) As I say - it's fine with Carte and Kstars. If I click on Dubhe it Identifies it as the scope (Mount) You can see from the second screen shot that it knows where the scope is pointing. I have attached the current log and two screenshots I have tested the INDIGO server with both Carte du Ciel and Kstars so I know the fall-back protocol is working fine. On the occasions that it has connected, if I issue a slew from another client, the stellarium scope position tracks to follow the slew. It has connected about 3 times out of 50 but would not issue a slew when I hit cmd+1. Log.txt shows it's done something as all the devices are listed. When I hit "Connect" it sits there sayin "Connecting" apparently never getting connected. I have tried many configuration variations with the telescope plugin. If it sees a legacy INDI client it falls back to support that protocol. Indigo server provides a kind of superset of INDI.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |