Skip to content

18. Using WebConnect

Gord Tulloch edited this page Nov 12, 2026 · 1 revision

18. Using WebConnect

Status: early build. WebConnect is a first-party plugin that is still being built. The pairing, sign-in and live-update foundations exist and are tested, and the first operating screen is in, but the rest of the operating screens are not finished and it has not yet been tried in a real browser. This article describes what WebConnect is designed to do; the plugin's own changelog says exactly what is and is not done.

WebConnect lets you operate a running Galileo observatory from any web browser — a laptop at the kitchen table, a tablet, a Chromebook, a screen in the observatory — with nothing to install. It is the web counterpart of the phone and tablet apps in 19. Using MobileConnect for iOS and Android, and offers the same level of control.

The idea is that the observatory is already set up and running. WebConnect lets you watch it and operate it; it never lets you configure it. Equipment, Observatories, safety limits and options stay on the Galileo desktop.

Contents


What you can do

Everything you would do during a night at the computer: see the state and activity timeline of every Pier, connect and operate devices, capture and preview images, find and centre a target, plate solve, focus (manually or automatically), guide, manage a meridian flip, run and edit sessions and the schedule, browse recent sessions and frames, respond to a safety event, and stop everything with the always-available emergency stop.

State is pushed to the browser as it changes, so you do not need to refresh the page. The layout is tablet-first but also works on a desktop browser and, reduced, on a phone, and has a night-vision (red) theme.

What you cannot do

WebConnect has no configuration. A browser is never granted permission to change equipment profiles, Observatories, Piers, safety rules, Options or plugin settings; those stay on the Galileo desktop (or reach other computers through 17. Using NodeConnect). Closing the browser tab, or losing the connection, never stops imaging — the exception is a manual motion you are holding down, which stops when you let go or the connection drops.

WebConnect is for your own network (or a VPN you already run). It does not provide internet access, port forwarding or a cloud relay, and it does not work offline.

Where it runs

WebConnect runs on the Master — the observatory computer — and is the single web address for the whole installation.

  • Astroberry (the main setup): WebConnect runs as a service on an Astroberry controller, behind Astroberry's own web server, at https://<device name>.local/galileo/, with a Galileo entry in Astroberry Manager. It shares the device's name and certificate with the rest of Astroberry.
  • Self-hosted: on a Master that is not an Astroberry system, the plugin starts and supervises its own web server with its own HTTPS port.

Installing

Install webconnect from Options > Plugins, then open Options > WebConnect. On Astroberry the plugin is installed from the Galileo package repository instead; see the project's Astroberry documentation. It uses Galileo's Connect Link for the network side, so Connect Link must be enabled on the Master.

Approving a browser

A browser can only sign in after a person has approved it on the Master.

  1. Open the WebConnect address in the browser and ask to connect.
  2. A short confirmation code is shown in the browser and the same code appears on the Master. Compare them.
  3. On the Master, open Options > WebConnect and approve the request.

The approved browsers are listed on that page, where any of them can be revoked at once. There is no separate account system: the approved clients are the sign-ins. Sessions time out after a period you set.

Viewers, operators and the control lease

Each approved browser is a Viewer (can see everything, change nothing) or an Operator (can also operate). Only one controller can drive a Pier at a time, through a control lease shared by the desktop, the phone apps and the browser, so two people cannot give a mount conflicting commands. Any number of viewers can watch. Destructive operations ask for confirmation, and everything done from a browser goes into an audit log on the Master.

Several computers: one address

If you use NodeConnect to link several Galileo computers, the browser talks only to the Master, which shows its own Piers and, through itself, the Piers of every paired spoke. The spoke must allow it when it pairs; a spoke that has not shows as view-only or not at all, and is unavailable if the Master is down (the spoke keeps imaging).

Outreach: sharing the live image

At a club or public event, the owner can open an outreach event on the Master. Visitors scan a QR code with their phone, land on a simple page in their browser — no app, no account, no sign-in — and see the live image of the Pier or Piers you chose to share, updated as each frame completes, and can switch between them. They can see nothing else and control nothing.

An event is closed by default, ends on a timer, runs on a separate network from your control network, and needs a certificate for the outreach address so the page is served over HTTPS. The same event can also offer images to the phone apps.

Setting up an outreach event

Outreach is set up on Options > Outreach on the Master, and needs Connect Link to be on. An event is off until you open it, lasts the time you set and then ends by itself, and reaches only devices on the guest Wi-Fi you name there (the address range you give must be a private one, so nothing on the internet can get in). You choose which Piers to offer; visitors see only the Observatory and Pier name and a picture with no file details in it.

Open event starts it. The Event display then shows a QR code for the guest Wi-Fi and one for each way of joining. Extend, End event, Eject all guests and New secret are beside it. Nothing about an event is kept: ending it, turning Connect Link off or restarting Galileo cuts everyone off. The ways of joining come from the WebConnect and MobileConnect plugins, so a visitor can join only once one of them is installed and working (see the status notes in those articles).

Safety and security

  • Viewer and Operator roles, a shared control lease, confirmation on destructive operations, a held-motion deadman and an audit log.
  • Browsers sign in over HTTPS with a token that was approved on the Master; nothing answers an unapproved browser (outside an outreach event).
  • Every operation goes through the same services and safety checks as the desktop. A browser can acknowledge a safety event but cannot disable the safety monitor or override a mount limit.

Limitations

  • It is not finished: see the status note at the top.
  • No configuration, no offline use, and no FITS processing in the browser (previews are rendered on the observatory computer; downloading a FITS frame is an explicit action).
  • It is not a remote-desktop view of the Galileo application. System functions that Astroberry already provides — INDI driver management, terminal, updates, Wi-Fi, backup — stay in Astroberry Manager.
  • Every plugin control has built-in help (press F1 or the ? button).

Clone this wiki locally