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
  • Brite
  • 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 - Status | Demo | Docs | Install
  1. Cloudron Forum
  2. Support
  3. IMAP Connection Timeout after migration to Bare-Metal Installation

IMAP Connection Timeout after migration to Bare-Metal Installation

Scheduled Pinned Locked Moved Unsolved Support
2 Posts 1 Posters 8 Views 1 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.
  • H Offline
    H Offline
    hakunamatata
    wrote last edited by hakunamatata
    #1

    Environment:

    • Hardware: Mini PC (Bare-metal)
    • OS: Ubuntu 24.04.4
    • Cloudron Version: 9.1.3
    • Internal IP: 10.69.69.69
    • Router/DNS/Firewall IP: 10.69.69.1
    • Cloudron Mailserver: my.domain.tld

    Problem Description:
    I recently migrated my Cloudron installation from a Synology VM to a bare-metal install. Since then, Paperless-ngx cannot connect to the internal Cloudron Mail server via the public FQDN (my.domain.tld) to ingest email attachments for processing.

    Diagnostics:

    • nc -zv 10.69.69.69 993 from the app terminal succeeds.
    • nc -zv my.domain.tld 993 from the app terminal does not receive any response.
    • Per the paperless mail.log [ERROR] [paperless_mail] Error while retrieving mailbox Paperless: [Errno 110] Connection timed out.
    • Inside the container, the domain resolves to the Public IP rather than the local IP, leading to a loopback failure on my UniFi UDM SE.
    • Attempts to override this via /etc/unbound/unbound.conf.d/custom.conf have not been successful in getting the container to prioritize the local IP.
    # Forward all queries to the network's internal DNS 10.69.69.1. 
    forward-zone:
      name: "."
      forward-addr: 10.69.69.1
    

    Request:
    What is the recommended Cloudron-native way to force apps to resolve the Mail server to the local host IP (10.69.69.69) to avoid Hairpin NAT issues, specifically for a bare-metal installation?

    Note:
    I already have a local DNS A record set up on the Unifi UDM SE that points the local IP (10.69.69.69) to domain.tld.

    1 Reply Last reply
    0
    • H Offline
      H Offline
      hakunamatata
      wrote last edited by
      #2

      Disregard, it was a firewall issue on my DMZ VLAN. Please close/delete this topic.

      1 Reply Last reply
      0

      Hello! It looks like you're interested in this conversation, but you don't have an account yet.

      Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

      With your input, this post could be even better 💗

      Register Login
      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