Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. MiroTalk
  3. Initial setup question RE: Cloudflare proxy disabled --> Port forward SFU TCP+UDP?

Initial setup question RE: Cloudflare proxy disabled --> Port forward SFU TCP+UDP?

Scheduled Pinned Locked Moved MiroTalk
4 Posts 3 Posters 628 Views 3 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • coniunctioC Offline
    coniunctioC Offline
    coniunctio
    wrote on last edited by
    #1

    I did not see any mention of this on the Cloudron docs page for MiroTalk and hopefully this is a simple initial setup question:

    Does the warning about disabling Cloudflare proxying on the app's Location settings page also mean that I need to port forward to port 40000 per the default settings?

    Locations
    subdomain.mycloudron.com
    
    SFU TCP Ports (100 ports) 40000 to 40099
    40000
    Cloudflare proxying must be disabled for the app's domain to access this port
    
    SFU UDP Ports (must be same as TCP ports) (100 ports) 40000 to 40099
    40000
    
    Cloudflare proxying must be disabled for the app's domain to access this port
    
    1 Reply Last reply
    0
    • J Offline
      J Offline
      joseph
      Staff
      wrote on last edited by
      #2

      I guess you are on an internal network? If so, port 40000 has to be port forwarded as well. On a public network, you have to make sure 40000 is open in any Cloud firewall.

      The Cloudflare warning exists because Cloudflare only forwards http (port 80, 443).

      1 Reply Last reply
      3
      • nebulonN Offline
        nebulonN Offline
        nebulon
        Staff
        wrote on last edited by
        #3

        In fact, you need to port forward all ports from 40000 ... 40099 as mirotalk needs the port range to work reliably!

        1 Reply Last reply
        2
        • coniunctioC Offline
          coniunctioC Offline
          coniunctio
          wrote on last edited by
          #4

          Thank you! I will test this following your clarification.

          1 Reply Last reply
          0
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          • Login

          • Don't have an account? Register

          • Login or register to search.
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • Bookmarks
          • Search