Station Troubleshooting¶

Connectivity
- The MobileConnect Station is not showing in the MobileConnect Manager list of Stations.
- The MobileConnect Station has status “Not Running” in the Manager interface.
MobileConnect Station update
- The MobileConnect Station update was interrupted before it was completed.
- The MobileConnect Station update is not started after clicking “Start update” button.
MobileConnect Station Network Configuration
- You configured the IP address 192.168.0.10 on the LAN2/PoE/Streaming port or LAN3/Ctrl port.
- You configured an IP address in the subnet 192.168.0.0 on the MCSv1 LAN2 or LAN3.
MobileConnect Station Channel Configuration
- All Station channels are greyed out in the Manager “Mobile App Configuration” page.
MobileConnect Station Accessing Local Admin Interface

Connectivity ¶

The MobileConnect Station is not showing in the MobileConnect Manager list of Stations.¶

Check the Station network connections and configuration.
- If you configured a static or dynamic IP address in the 192.168.0.x subnet -> you need to connect both the streaming and control port to the same network, for the Station to be able to connect to the Manager.
- Do not use the address 192.168.0.10 on your streaming or control interfaces.
- If you use DHCP and 192.168.0.x/24, make sure that your DHCP-Server is not leasing 192.168.0.10.
- If you are using one port solution with the manager accessible via routing on the streaming interface and the control port is connected -> disconnect the control port.
In case you recently updated your Manager, make sure that your firewall allows port 8383 to be accessible from the MobileConnect Station.
Try rebooting the Station.
Make sure the DNS configuration is correct, see Step 1. Configure your network.
In case you are not using DNS and configured the Manager IP address on the Station (possible since Station firmware version 6.2.0)
- Make sure the Station is configured in Manager Mode, by opening the local admin interface and checking in General.
- Make sure the Manager IP address is correct and the Station is connected to the correct network over the Control port. If your control network is configured with a static IP address but not connected, the Station cannot establish a connection with the Manager.
- Reboot the Station.
- In case the issue persists, contact us at mc-support@sennheiser.com and send us your Station’s log file. You can download it using the local admin interface.
In case you have a MobileConnect Manager version 1.0.0 or 1.1.0:
- Make sure the MobileConnect Manager is running before the MobileConnect Stations or reboot the MobileConnect Stations, after the MobileConnect Manager is started.
- Open the local admin interface and check the Station firmware version. Station firmware version 6.1.0 is not compatible with Manager 1.0.0 or 1.1.0 due to the enhanced security feature.
- Check if your Manager is the latest version and consider updating it. For more see MobileConnect Manager Upgrade and Redeploy.
- You can also downgrade the Station firmware, contact us at mc-support@sennheiser.com.

The MobileConnect Station has status “Not Running” in the Manager interface.¶

Check the Station network cables are connected, and the Station network configuration is correct.
In case you recently updated your Manager, make sure that your firewall allows port 8383 to be accessible from the MobileConnect Station.
Was the Station authorization recently reset using the local admin interface (available since Station firmware version 6.1.0)? If yes, remove the Station from the Manager and restart it. For more information about authorization see Security & Authorization.
Was the Station sent back for repairs? If yes, remove the Station from the Manager and restart it.

MobileConnect Station update ¶

The MobileConnect Station update was interrupted before it was completed.¶

If the MobileConnect Station is not updated and there are no errors on the Manager interface after the interruption → restart the MobileConnect Station and try again.
The MobileConnect Manager is showing an error after the interruption → restart the MobileConnect Station and try again.
The error message is still shown after restarting the MobileConnect Station → restart the MobileConnect Manager.

docker restart $(docker ps -a -q)

The MobileConnect Station update is not started after clicking “Start update” button.¶

Restart the MobileConnect Manager Docker containers and try again.

docker restart $(docker ps -a -q)

Note: this may interrupt streaming.

MobileConnect Station Network Configuration ¶

You configured the IP address 192.168.0.10 on the LAN2/PoE/Streaming port or LAN3/Ctrl port.¶

This port is used for the local administration interface and using it on the network ports may cause the local interface to become inaccessible.
To fix → remove the network connection of the streaming interface (LAN2/PoE/Stream port) and perform a reset followed by a reboot.
Alternatively change the IP address via the MobileConnect Manager.

You configured an IP address in the subnet 192.168.0.0 on the MCSv1 LAN2 or LAN3.¶

The local admin interface may become inaccessible.
To access it again via LAN1 → unplug the LAN2 and LAN3 cables.

MobileConnect Station Channel Configuration ¶

All Station channels are greyed out in the Manager “Mobile App Configuration” page.¶

Check whether your MobileConnect Station is “Running” in the Stations page.
Open the Station page, by selecting it from the Stations list. Select “Network”. Check the network configuration of your Station(s) and make sure that the Streaming network interface is connected and has a valid IP address (and not a link local address).
Open the Station page, by selecting it from the Stations list. Select a channel and enter the channel page. Make sure the “This channel is enabled” checkbox is selected.

MobileConnect Station Accessing Local Admin Interface ¶

The browser shows error “Your connection is not private”.¶

With Station firmware version 6.2.0 and higher, when you first open the local admin interface, the browser reports:

Google Chrome: “Your connection is not private”.
Mozilla Firefox: “Your connection is not secure”.

The local admin interface uses a self-signed certificate which is not known to your browser. You need to confirm the security warning by:

Google Chrome: select “Advanced” and “Proceed to 192.168.0.10 (unsafe)”.
Mozilla Firefox: select “Advanced” and “Accept the Risk and Continue”.

The browser shows error “This site can’t be reached”.¶

The browser reports an error when try to open the local admin interface on https://192.168.0.10.

Try opening http://192.168.0.10/.
Try opening http://192.168.0.10/ in an incognito window.
The Station is not running. Check whether the Station’s LED is green.
The Station is not accessible on this IP address. Do a ping test (ping 192.168.0.10) and check how to connect to the local admin interface in Configure Your Station Using the Local Admin Interface

The browser reports an error when try to open the local admin interface on http://192.168.0.10.

Check if the browser redirects the request to https, by clicking on the URL. If it’s the case, you can avoid that by clearing the browsing cache and browsing data of your browser.
Alternatively you can open http://192.168.0.10/ in an incognito window.

Downloading the Station logs doesn’t work.¶

The log download may take up to 1 minute.