Skip to content
DataMiner DoJo

More results...

Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors
Search in posts
Search in pages
Search in posts
Search in pages
Log in
Menu
  • Blog
  • Questions
  • Learning
    • E-learning Courses
    • Open Classroom Training
    • Certification
      • DataMiner Fundamentals
      • DataMiner Configurator
      • DataMiner Automation
      • Scripts & Connectors Developer: HTTP Basics
      • Scripts & Connectors Developer: SNMP Basics
      • Visual Overview – Level 1
      • Verify a certificate
    • Tutorials
    • Video Library
    • Books We Like
    • >> Go to DataMiner Docs
  • Expert Center
    • Solutions & Use Cases
      • Solutions
      • Use Case Library
    • Markets & Industries
      • Media production
      • Government & defense
      • Content distribution
      • Service providers
      • Partners
      • OSS/BSS
    • DataMiner Insights
      • Security
      • Integration Studio
      • System Architecture
      • DataMiner Releases & Updates
      • DataMiner Apps
    • Agile
      • Agile Webspace
      • Everything Agile
        • The Agile Manifesto
        • Best Practices
        • Retro Recipes
      • Methodologies
        • The Scrum Framework
        • Kanban
        • Extreme Programming
      • Roles
        • The Product Owner
        • The Agile Coach
        • The Quality & UX Coach (QX)
    • DataMiner DevOps Professional Program
  • Downloads
  • More
    • Feature Suggestions
    • Climb the leaderboard!
    • Swag Shop
    • Contact
      • General Inquiries
      • DataMiner DevOps Support
      • Commercial Requests
    • Global Feedback Survey
  • PARTNERS
    • All Partners
    • Technology Partners
    • Strategic Partner Program
    • Deal Registration
  • >> Go to dataminer.services

Element Replication – is it possible to avoid using TCP port 80?

Solved1.84K views12th February 2021firewall replication security timeout
7
Alexander Gorbunov [SLC] [DevOps Advocate]988 10th February 2021 2 Comments

Hi Dojo,

We are trying to set up a DMA in a DMZ which will replicate several elements from the main cluster. For security reasons, it is undesirable to allow communication over well known ports, especially TCP port 80. However, it seems that DataMiner needs port 80 for some transactions when a replicated element is starting up. If I block port 80 and restart the element, it goes into timeout with the following in SLReplication.txt log:

Connection failed: Could not auto-detect URI for 10.5.1.18: timeout

I tried enabling HTTPS on both DMAs, but this seemed to have no effect, DataMiner still tries to use port 80 for replication, according to Wireshark traces.

Here is the Wireshark statistics for conversations between agents running replication:

Is this the intended behavior? Is there a way to avoid using TCP80 for replication?

Thank you.

Alexander Gorbunov [SLC] [DevOps Advocate] Selected answer as best 12th February 2021
Alexander Gorbunov [SLC] [DevOps Advocate] commented 10th February 2021

Update:
In a test setup we were able to run replication using only TCP 443 and 8004. To achieve that, HTTPS had to be configured on the hosting DMA and polling address of the replicated element had to be in the form [domain_name]:443.

Alexander Gorbunov [SLC] [DevOps Advocate] commented 10th February 2021

Update:
We also confirmed is possible to use a custom port instead of TCP 80 by configuring a proxy between the hosting and the replication DMA.
The proxy needs to do the following:
– Listen to the custom port and forward it to [hosting_dma_ip]:80;
– Listen to port 8004 and forward it to [hosting_dma_ip]:8004.
We used Linux based NGINX as a proxy in our test.

1 Answer

  • Active
  • Voted
  • Newest
  • Oldest
8
Wouter Demuynck [SLC] [DevOps Advocate]5.91K Posted 10th February 2021 0 Comments

Hi Alexander,

Port 80 and/or 443 are indeed used while setting up the connection between the DataMiner Agent replicating the element and the DataMiner Agent hosting the source element. Main purpose is to find out the port DataMiner is listening on (typically 8004).

That said, you can provide this probing port in the replication settings by e.g. specifying "ipaddress:443" to do the probing via HTTPS only.

I'm not aware of a way to fully eliminate the use of port 80/443 and have the connection go immediately through port 8004. (No way directly configurable through Cube at least)

Alexander Gorbunov [SLC] [DevOps Advocate] Selected answer as best 12th February 2021
Please login to be able to comment or post an answer.

My DevOps rank

DevOps Members get more insights on their profile page.

My user earnings

0 Dojo credits

Spend your credits in our swag shop.

0 Reputation points

Boost your reputation, climb the leaderboard.

Promo banner DataMiner DevOps Professiona Program
DataMiner Integration Studio (DIS)
Empower Katas

Recent questions

When using the Setter = true attribute, will the copy action always be executed first? 1 Answer | 1 Vote
Multiple Set on Table parameters for DVE’s 0 Answers | 1 Vote
DOM Definition relations returned in Definition query 0 Answers | 2 Votes

Question Tags

adl2099 (115) alarm (62) Alarm Console (82) alarms (100) alarm template (83) Automation (223) automation scipt (111) Automation script (167) backup (71) Cassandra (180) Connector (109) Correlation (68) Cube (150) Dashboard (194) Dashboards (188) database (83) DataMiner Cube (57) DIS (81) DMS (71) DOM (140) driver (65) DVE (56) Elastic (83) Elasticsearch (115) elements (80) Failover (104) GQI (159) HTTP (76) IDP (74) LCA (152) low code app (166) low code apps (93) lowcodeapps (75) MySQL (53) protocol (203) QAction (83) security (88) services (51) SNMP (86) SRM (337) table (54) trending (87) upgrade (62) Visio (539) Visual Overview (345)
Privacy Policy • Terms & Conditions • Contact

© 2025 Skyline Communications. All rights reserved.

DOJO Q&A widget

Can't find what you need?

? Explore the Q&A DataMiner Docs

[ Placeholder content for popup link ] WordPress Download Manager - Best Download Management Plugin