Advanced VPN and File Transfer Troubleshooting – Starfront Observatories

Overview

Your Starfront VPN profile is configured to provide limited access to your assigned observatory device or approved Starfront resources. It is not designed to route all of your normal internet traffic through Starfront.

If your VPN connects successfully but remote access or file transfers feel slow, that does not always mean the VPN itself is broken. VPN performance depends on the full connection path between your device and the remote observatory equipment.

That path may include:

Your computer, tablet, or phone
Your home Wi-Fi or Ethernet
Your home router/modem
Your internet provider
Regional or international internet routing
The Starfront VPN connection
The observatory network
Your assigned telescope device

The slowest or least stable part of that path usually determines the final performance.

Why VPN and File Transfer Speeds Can Vary

The VPN connection is only one part of the path

A VPN creates a secure connection between your device and the observatory network. However, the VPN still depends on your local device, your home network, your internet provider, internet routing, and the remote astronomy device.

A successful VPN connection means the secure tunnel is working. It does not guarantee that every file transfer will run at high speed.

Common causes of slow VPN or file transfer performance include:

Weak home Wi-Fi signal
Router or modem issues
ISP routing problems
Cellular or Starlink variability
International distance and latency
Packet loss
VPN packet fragmentation
Security filtering or traffic inspection
Slow storage on the remote astronomy device
Limitations of SMB/network file sharing

ASIAIR and Seestar file transfers use SMB

Many astronomy devices, including ASIAIR and Seestar systems, use SMB/network sharing for file transfers.

SMB can work well on a local network, but it can be sensitive to latency, packet loss, Wi-Fi quality, router behavior, and ISP routing when used over a VPN. This means your VPN may be connected and working correctly, while file transfers may still be slower than expected.

Because ASIAIR and Seestar devices provide limited file transfer options, SMB may be the only available method for accessing image files directly from the device. In those cases, the best improvements usually come from improving the local connection path and using the most stable VPN settings available.

Small astronomy devices may not transfer files as fast as a full computer

Devices such as ASIAIRs, Seestars, Raspberry Pi-based systems, small ARM computers, mini PCs, and embedded telescope controllers may have limited processing power, storage speed, or network performance.

These devices may work very well for telescope control while still being slower for file transfers than a desktop computer, server, or NAS.

Possible device-side limitations include:

Wi-Fi instead of Ethernet
Small internal antennas
Slower internal storage
USB storage limitations
microSD card limitations
Embedded processor limitations
SMB server limitations on the device

Recommended Troubleshooting Steps

1. Test from a cellular hotspot

One of the most useful tests is to connect your computer to your phone's cellular hotspot and try the VPN again.

If the VPN or file transfer works better over cellular than it does over your home internet, the issue is likely related to your home internet provider, home router, modem, Wi-Fi, or local network configuration.

This test is helpful because the Starfront VPN and remote device remain the same. Only your local connection path changes.

2. Test from another computer or device

If possible, try the same VPN connection from another computer, tablet, or phone.

This can help determine whether the issue is specific to one device.

Things that can affect one computer but not another include:

Local firewall settings
Security software
Antivirus network filtering
Another VPN app running in the background
Outdated VPN client software
Wi-Fi adapter issues
Operating system network settings

3. Use Ethernet instead of Wi-Fi when possible

If your computer is connected to your home network over Wi-Fi, try using Ethernet instead. The most reliable test setup is your computer connected directly to your home router/modem with an Ethernet cable.

Home Wi-Fi issues are one of the most common causes of slow or inconsistent VPN performance. This is especially true when using mesh Wi-Fi, weak signal areas, Wi-Fi extenders, or crowded 2.4 GHz networks.

If Ethernet performs better than Wi-Fi, the VPN is probably not the main issue. The bottleneck is likely your home Wi-Fi connection.

4. Reboot your modem, router, and computer

Before making advanced changes, restart your local network equipment in this order:

Disconnect the VPN.
Reboot your modem or ISP gateway.
Reboot your router, if separate.
Reboot your computer.
Reconnect to the VPN.
Test again.

This can clear temporary router, NAT, DNS, or session issues.

5. Avoid downloading directly into cloud-synced folders

Do not test VPN file transfer speed by downloading directly into cloud-synced folders such as:

OneDrive
iCloud Drive
Dropbox
Google Drive
Network-mounted folders

These services may begin uploading or indexing files while you are still downloading them from the observatory device. This can make the VPN transfer appear slower than it really is.

For testing, download to a normal local folder first, such as Downloads, Desktop, or C:\Temp. On macOS, use ~/Downloads or ~/Desktop. After the transfer completes, you can move the files to cloud storage if needed.

6. Transfer fewer files at once when possible

SMB transfers often perform worse when copying many small files compared with fewer large files.

If possible, transfer a smaller batch of files first to test performance.

When the device allows it, transferring one larger file or a compressed archive is usually more efficient than transferring hundreds of small files individually.

Some astronomy devices may not allow files to be compressed directly on the device. In that case, simply test with a smaller number of files first.

7. Test outside peak imaging hours

During clear nights, many customers may be connected, imaging, using remote desktop, and transferring files at the same time.

If your connection feels slow during peak imaging hours, try testing again during the day or during a cloudy period.

If speeds improve significantly outside peak hours, overall network activity or remote device activity may be contributing to the slowdown.

8. Temporarily disable router security or traffic-shaping features for testing

Some home routers inspect, prioritize, or filter traffic in ways that can slow VPN connections.

If you are comfortable checking your router settings, temporarily disable these features for a test:

QoS
Adaptive QoS
Gaming acceleration
Traffic analyzer
Parental controls
Web filtering
Threat protection
Deep packet inspection
VPN filtering
Smart security features

This is only recommended as a temporary test. If disabling one of these features improves performance, your router may be interfering with VPN traffic.

Common examples include ISP-provided routers, mesh systems, gaming routers, and routers with built-in security subscriptions.

9. Disconnect other VPN or privacy tools

Running more than one VPN or privacy tool at the same time can cause slow or unreliable connections.

For testing, disconnect or temporarily disable:

Other VPN apps
Cloudflare WARP
iCloud Private Relay
AdGuard VPN
NordVPN, ExpressVPN, Surfshark, or similar VPNs
Corporate VPN clients
Network filtering tools
Web protection tools

Only use the Starfront VPN while testing access to your observatory device.

10. Ask support about an adjusted MTU profile

Some networks do not handle VPN packet sizes well. This can cause slow transfers, stalled downloads, or inconsistent performance even though the VPN connects.

For some customers, Starfront support may provide a VPN profile with an adjusted MTU value of 1280.

This may help with:

Some home internet providers
ISP router/modem combo units
Cellular internet
Starlink
International connections
Networks that handle packet fragmentation poorly
Connections where downloads stall or behave inconsistently

Starfront does not recommend setting WireGuard MTU below 1280 on our UniFi-based VPN profiles.

Please do not edit your VPN profile unless Starfront support specifically asks you to do so.

DNS and Starfront VPN Profiles

Starfront VPN profiles typically do not include a custom DNS line because customers are normally connecting directly to their assigned device by IP address, for example 172.x.x.x. When connecting by IP address, DNS is not required.

Adding public DNS servers such as 1.1.1.1 or 8.8.8.8 usually does not improve VPN speed or SMB file transfer performance. DNS only affects name lookup. It does not improve the actual transfer speed once the VPN connection is established.

DNS may only matter if:

You are trying to connect by hostname instead of IP address
Normal websites stop resolving while the VPN is connected
Your local DNS settings are broken
Support specifically asks you to test a DNS setting

For normal Starfront device access by IP address, no DNS line is usually needed.

Limited-Access VPN Configuration

Your Starfront VPN profile is already configured to allow access only to your assigned observatory device or approved Starfront resources.

This is intentional.

The VPN is not designed to route all of your normal internet traffic through Starfront. It is configured this way for security, performance, and customer isolation.

Please do not modify the allowed IPs, routing settings, endpoint, or other VPN configuration values unless Starfront support specifically asks you to do so. Changing these settings may prevent the VPN from working correctly.

VPN Port Changes

Customers should not change the VPN endpoint port in their VPN profile unless Starfront support provides a new profile.

The VPN port must match the Starfront VPN server configuration. Changing the port locally will usually break the connection.

If alternate VPN ports are used in the future, they will be provided through new or updated VPN profiles from Starfront.

Information to Send Support

If you continue to experience slow VPN or file transfer performance, please send support the following information:

Your internet provider
Your location (state/country)
Are you using home internet, Starlink, cellular, hotel Wi-Fi, or work Wi-Fi?
Are you connected by Wi-Fi or Ethernet at home?
What device are you using to connect? (Windows/Mac/iPad/phone/etc.)
What VPN client are you using?
What remote device are you connecting to? (ASIAIR, Seestar, mini PC, Raspberry Pi, etc.)
Are you using remote desktop, SMB/network file sharing, or both?
Approximate file transfer speed
Does the issue happen all the time or mainly at night?
Have you tested from a cellular hotspot?
Have you tested from another computer or device?
Have you tested with Ethernet instead of Wi-Fi?
Have you rebooted your modem/router and computer?
Screenshot of a speed test, if available

This information helps support determine whether the issue is most likely related to the local network, home router, internet provider, VPN packet handling, observatory network, or the remote astronomy device itself.

Summary

A working VPN connection does not always guarantee fast file transfers.

For ASIAIR, Seestar, and similar astronomy devices, file transfers often rely on SMB/network sharing. SMB can be sensitive to latency, packet loss, Wi-Fi quality, ISP routing, router behavior, and VPN packet handling.

The best troubleshooting steps are:

Test from a cellular hotspot.
Test from another computer.
Use Ethernet instead of Wi-Fi.
Reboot modem/router/computer.
Avoid cloud-synced download folders.
Transfer fewer files at once.
Temporarily disable router security/QoS features for testing.
Disconnect other VPN/privacy tools.
Ask support about an MTU 1280 compatibility profile.

If the same VPN works normally from another connection or device, the slowdown is likely related to the local connection path rather than the VPN profile itself.