Support

AXIS Secure Remote Access or Camera Station Client Cannot Connect

This guide addresses AXIS Camera Station works locally but a remote client cannot connect in the order technical support would test it: preserve what matters, open the correct screen, correct the proven cause and verify the result.

Remote Client

AXIS network camera
AXIS support jobs usually come back to the camera identity, Camera Station workflow, network path and user permissions rather than one flashy feature.

Summary

Follow the four stages below to diagnose AXIS Camera Station works locally but a remote client cannot connect without losing evidence, configuration or device ownership.

Applies to

  • AXIS Camera Station
  • AXIS Secure Remote Access users

Difficulty and time

Difficulty: Advanced

Estimated time: 25 to 60 minutes

What you will need

  • The exact model and current firmware or app version
  • Administrator access where authorised
  • A photo or screenshot of the current status
  • One controlled test case and its exact time

What this guide covers

  • Preserve and reproduce the fault
  • Open the correct diagnostic screen
  • Correct the proven cause
  • Verify and document the result

Use this page when AXIS Camera Station works locally but a remote client cannot connect. It includes the menu or screen to look for, the status that matters and a repeatable proof test.

Exact labels can differ between recorder, controller, app and firmware versions. If the named screen is not present, do not guess at destructive options; note the model and current version for support.

Before you start

Protect the current system and record a baseline before changing anything.

  • Write down the exact symptom: the site/server is missing, offline or rejects the remote MyAxis user.
  • Photograph the current status, error text, wiring or timeline as applicable.
  • Record the last known working time and anything changed immediately before the fault.
  • Record server identity, licence state and current MyAxis ownership before removing accounts or reinstalling.
Important

Do not rebuild a working server to fix a remote-account symptom

Reinstallation can complicate databases, licences and ownership. Prove the local server first.

If the required option is missing or the result does not match this guide, stop and identify the exact model before continuing.

What usually causes this

  • Server has no internet/DNS
  • Secure Remote Access is disabled
  • Wrong MyAxis account/organisation
  • User lacks Camera Station permissions

Step 1: Preserve the current state and reproduce the fault

Begin with a repeatable baseline so you know whether a later change genuinely helped.

  • Reproduce the problem once and record: the site/server is missing, offline or rejects the remote MyAxis user.
  • Note whether every device or user is affected, or only one.
  • Compare one working path with the failing path if a comparison exists.
  • Record server identity, licence state and current MyAxis ownership before removing accounts or reinstalling.

Step 2: Open the correct screen and inspect the evidence

The primary diagnostic location is AXIS Camera Station Service Control/Management > Secure Remote Access, then client > Connect > Remote. Do not change anything until the displayed state is recorded.

  • Open AXIS Camera Station Service Control/Management > Secure Remote Access, then client > Connect > Remote. Menu wording can vary by model and firmware; use the nearest equivalent label.
  • Prove the Camera Station server and cameras are healthy on the local network.
  • Confirm Secure Remote Access is enabled and signed in with the intended MyAxis account.
  • Check the remote user exists with the required Camera Station permissions.

Step 3: Correct only the cause you proved

Use the matching correction below. Make one change, save it, then repeat the same test.

  • Correct server internet, DNS and time before changing client settings.
  • Sign the server into the intended MyAxis organisation/account and enable Secure Remote Access.
  • Invite or assign the remote user with least required privileges.
  • Update compatible client/server versions through the supported AXIS path.

Step 4: Verify, monitor and document the handover

A saved setting is not proof. Test the real outcome locally first, then test any app, cloud or client path separately.

  • Connect locally first with the user.
  • Test remote sign-in from a different internet connection.
  • Open live view and recorded video according to permissions.
  • Confirm a user without export/admin rights cannot access those functions.
Worked example

Controlled support test

Situation: The reported symptom was: the site/server is missing, offline or rejects the remote MyAxis user.

Solution used: The current state was recorded in AXIS Camera Station Service Control/Management > Secure Remote Access, then client > Connect > Remote, one matching correction was made, and the same test was repeated.

Why this was chosen: This separated the proven cause from unrelated settings.

Installation notes: The final screenshot and test time were saved with the handover record.

Official reference used for this guide

Menu names differ between releases. Confirm model-specific behaviour in AXIS product support documentation before firmware, reset, storage or security-sensitive work.

Common mistakes

  • Changing several settings before repeating the original test.
  • Using a factory reset, initialise or format option as an early troubleshooting step.
  • Treating an app symptom as proof that the local hardware or recording has failed.
  • Failing to record the model, version, exact error and test time before escalation.
  • Assuming similar-looking models use identical menus or features.

Troubleshooting table

Symptom What to check What to do next
the site/server is missing, offline or rejects the remote MyAxis user server offline, Secure Remote Access disabled, wrong MyAxis organisation, missing user permission or version mismatch Open the named diagnostic screen, record the displayed state and use the matching correction above.
The named menu is not visible Different firmware, permissions or model capability Do not substitute a destructive menu. Capture the model and version and use its official manual.
The change saves but the fault remains The selected cause was not the root cause Undo the change if appropriate, return to the baseline and compare the failing path with a working one.
Local test works but app or client test fails Account, permission, cloud or remote-network path Keep the proven local configuration and diagnose the remote path separately.
Problem returns later Intermittent power, cable, storage, network or schedule condition Record the new failure time and status; correlate it with logs, events and the last known working interval.

When to contact support

Contact SecurityWholesalers support when local client operation is proven but the intended remote account still cannot see or connect to the server.

Send the order number if available, exact model, firmware or app version, screenshot of AXIS Camera Station Service Control/Management > Secure Remote Access, then client > Connect > Remote, the failure time, and the result of the local proof test.

Related support guides

Related buying guides

Relevant product categories

Still stuck?

Need help choosing or setting up a system? Contact SecurityWholesalers support with your order number, product model and a clear description of the issue.

Frequently asked questions

  • Where should I click first for AXIS Secure Remote Access not working?

    Start at AXIS Camera Station Service Control/Management > Secure Remote Access, then client > Connect > Remote. Record the existing state before changing it because labels and available options can vary by model and firmware.

  • What should I look for on that screen?

    Look for server running state, Secure Remote Access enabled/connected status, MyAxis organisation and user role.

  • What must I avoid changing during the first check?

    Reinstallation can complicate databases, licences and ownership. Prove the local server first.

  • How do I prove the correction worked?

    Use the intended user from an off-site connection to view permitted live and recorded video, then confirm restricted functions stay restricted.

  • Why might my menu names look different?

    Recorder, controller, camera, app and firmware releases can use different labels. Use the closest equivalent only when its function is clear; otherwise record the model and version for support.

  • Should I factory-reset the device?

    Not as an early step. A reset may erase users, network settings, recording configuration, licences or cloud ownership. Back up the configuration and confirm the recovery plan first.

  • What should I send technical support?

    Send the exact model and version, screenshot of AXIS Camera Station Service Control/Management > Secure Remote Access, then client > Connect > Remote, exact error text, failure time, what changed before the fault and the result of the controlled local test.

  • Can configuration changes recover data or events that were never recorded?

    No. A correction can restore future operation, but it cannot recreate footage, alarm events or access transactions that were never stored.

Further Reading
Guide Page AXIS Support Guides Overview Overview Guide Page Hikvision Support Guides Guide Page HiLook Support Guides

We make product support and ordering easy! Reach out to our help team :)
Trade Customers: Log In or Register to Unlock Even Better Prices.

Save & Share Cart
Your Shopping Cart will be saved and you'll be given a link. You, or anyone with the link, can use it to retrieve your Cart at any time.
Save Cart & Generate Link
Send Cart in an Email Done! close
Empty cart. Please add products before saving :)

Back Save & Share Cart
Your Shopping Cart will be saved with Product pictures and information, and Cart Totals. Then send it to yourself, or a friend, with a link to retrieve it at any time.
Send Cart Email
Your cart email sent successfully :)