Dedicated MinIO server

For some use cases, you need to upload data from outside your server’s local network.

In this case, you can either use a dedicated server or cloud. Both let the device push data to your server while connected to an external WiFi access point (e.g. a remote WLAN or 3G/4G hotspot).


If you’re new to servers, we recommend that you start with an AWS S3 cloud. This way you do not have to consider port forwarding, firewalls etc. Once your setup is in place, you can always switch to a MinIO server later via an over-the-air update

Setting up a dedicated MinIO server (Windows)

To make a local MinIO server dedicated, you can port forward it:

  1. Log into your router settings (often via
  2. Go to the Port Forwarding section (often under WAN or Advanced)
  3. Create a new port forward entry (IPv4)
  4. In the ‘Local IP’, add the local network MinIO endpoint (e.g.
  5. In the local start/end port, add the MinIO endpoint port (e.g. 9000)
  6. Use the same MinIO port for the external start/end port (if relevant)
  7. Find your public WAN IP by googling “My IP” (e.g.
  8. Combine your public WAN IP with the MinIO port (e.g.
  9. Verify that you can connect to the server via e.g. your smartphone or other external network


The basic setup is intended for small-scale use. For use cases involving a larger number of CANedge2 devices, the setup may need to be modified for scalability


  • For corporate networks, you’ll often need to ask IT to open the relevant ports to provide access for the CANedge2. Typically this would be ports 9000 (MinIO) and port 123 (for the CANedge2 WiFi RTC syncing against an NTP server)
  • For corporate networks consult IT on firewalls and other factors that may block access
  • If you’re trying to connect to the external IP from within your server’s local network, you may need to use the local server endpoint instead
  • For more details, we generally recommend to check out the excellent MinIO docs