MobiusFlow Docs
Main WebsiteRaise a Support Ticket
  • Welcome
  • What is MobiusFlow®?
  • 📖User Guides
    • MobiusFlow Manager
    • MobiusFlow Toolbox
    • Getting Started
      • Administration
      • Service and Object Configuration
      • Diagnostics and Service Control
      • Running MobiusFlow via Docker
    • Deploying MobiusFlow in MobiusFlow Cloud
    • Deploying MobiusFlow On-Prem
      • Deploying MobiusFlow to approved Hardware (Using BalenaCloud)
        • Creating a Fleet
        • Adding Your First Device
        • Deploy MobiusFlow to Your Fleet
        • Adding Your Licence
        • Installed Services
        • Device Variables
        • Configure Networks
      • Deploying MobiusFlow on Customer Servers / Cloud
    • MobiusFlow Connectors
      • Configuring MobiusFlow for use with Connectors
      • MobiusFlow Official Connector
        • Connection Details and LED Indicators
        • Configuring a Connector
          • Home Page
          • Configure Network Page
          • Manage Certificates Page
          • Configure MQTT Page
          • Set Config Mode Password Page
          • About Page
        • Factory Resetting a Connector
      • MobiusFlow Raspberry Pi Connector
        • Converting Raspberry Pi to a MobiusFlow Connector
        • Configuring Raspberry Pi Connector
    • Technical Training Guides
      • Technical Training 1
  • ⚙️Technical Docs
    • MobiusFlow Cloud Hosted Environment
    • MobiusFlow Basics
      • MobiusFlow Overview
      • MobiusFlow Architecture
      • MobiusFlow Uniform Resource Identifiers (URIs)
      • Security
        • MobiusFlow Internal Security
      • Backup and Restore
      • Ports and Endpoints
    • MobiusFlow Engine API
      • Authorization
      • Discover
      • Node
      • Service
      • Object
      • Profiles
      • Command
      • Flows
      • Subscription
      • Licence
    • MobiusFlow Services
      • DALI Lighting
        • DALI via AFDWeb MQTT
      • LoRaWAN Local Network Server
      • MobiusFlow Connectors
      • INGY Lighting
      • Object Store
      • EnOcean Devices
        • EnOcean Equipment Profiles (EEPs)
    • Flows
      • Connecting the Flows to MobiusFlow Engine
      • Data Transfer between Flows and MobiusFlow Engine
      • Further Data Transfer between Flows and MobiusFlow Engine
      • Receiving and Sending Raw EnOcean Telegrams
    • Licencing
      • Licensing (v1.19.1 and later)
  • Glossary
Powered by GitBook
On this page
  • MobiusFlow with LoRaWAN Stack
  • Port Mappings (Simple)
  • Port Mappings (Advance)
  • Docker & Docker Routing
  • Full Mappings
Export as PDF
  1. Technical Docs

MobiusFlow Cloud Hosted Environment

Reference material for the environment in which MobiusFlow Cloud Instances exist

PreviousTechnical Training 1NextMobiusFlow Basics

Last updated 5 months ago

MobiusFlow with LoRaWAN Stack

It is optional to include the LoRaWAN Stack when specifying the hosting type on instance creation. This Stack will grant the ability to use the .

If included, an instance of and it associated infrastructure will be hosted in the background. Accessing this is not necessary to use the LNS, however it is accessible if required. Full details can be found within the .

Port Mappings (Simple)

The table below shows a simple overview illustrating how the ports are mapped. This is a simple overview suitable for most users.

Exposed Port
Internal
Usage
Version

8443

8443

Mobius Engine API

All

8080

8080

MobiusFlow UI (Toolbox)

All

1880

1880

Flows access

All

8883

1883

Suggested use for MQTT Broker. If the port is set to 1883 within the service, it will be accessible in the outside via 8883.

All

30815

30815

Free

All

30817

30817

Free

All

8081

8082

Chirpstack UI

MobiusFlow with LoRaWAN Stack

1700

1700

EU868 Chirpstack LoRaWAN Gateway Bridge

MobiusFlow with LoRaWAN Stack

1701

1700

US915_0 Chirpstack LoRaWAN Gateway Bridge

MobiusFlow with LoRaWAN Stack

1702

1700

US915_1 Chirpstack LoRaWAN Gateway Bridge

MobiusFlow with LoRaWAN Stack

Port Mappings (Advance)

Docker & Docker Routing

Different parts of the MobiusFlow solution run in different docker containers. These communicate via docker routing. Docker routing allows container names to be resolved in the Host OS, for example, to refer to the Mobius Engine API from the Host OS or a container that is not the mobius container, one could use mobius:8442 (container name followed by Host OS Port).

This means that, if communication between containers is required, the Host OS port and container is required. As such, these are included in the advanced port mappings table below.

Full Mappings

The table below gives a full description of the port mappings a MobiusFlow Cloud hosted environment is subject to.

Exposed Port
Host OS Port
Container Name
Internal
Usage
Version

8443

8442

mobius

8443

Mobius Engine API

All

8080

8080

toolbox

8080

MobiusFlow UI (Toolbox)

All

1880

1879

mobius

1880

Flows access

All

8883

1883

mobius

1883

Free - Normally MF MQTT Broker

All

30815

30814

mobius

30815

Free

All

30817

30816

mobius

30817

Free

All

8081

8082

chirpstack

8082

Chirpstack UI

MobiusFlow with LoRaWAN Stack Only

/

1884

mosquitto

1884

Chirpstack MQTT broker

MobiusFlow with LoRaWAN Stack Only

/

8090

chirpstack-rest-api

8090

Chripstack Rest API

MobiusFlow with LoRaWAN Stack Only

1700

1700

chirpstack-gateway-bridge-eu868

1700

EU868 Chirpstack LoRaWAN Gateway Bridge

MobiusFlow with LoRaWAN Stack Only

1701

1701

chirpstack-gateway-bridge-us915_0

1700

US915_0 Chirpstack LoRaWAN Gateway Bridge

MobiusFlow with LoRaWAN Stack Only

1702

1702

chirpstack-gateway-bridge-us915_1

1700

US915_1 Chirpstack LoRaWAN Gateway Bridge

MobiusFlow with LoRaWAN Stack Only

⚙️
MobiusFlow LoRaWAN LNS
Chirpstack
LNS Service documentation