Welcome to the Firewall Instructions Info Article

This article should be readable in 5 Minutes. We will explain how Meetical works under the hood and discuss potential firewall issues and their solution.

Meetical for Confluence Server uses a hybrid Server/Cloud approach to deliver a great product experience to you.

Meetical for Confluence Server works with Confluence Server (on premise). No suprise here. However, our Meetical Cloud Service running at app.meetical.io (on port 443) needs to be able to communicate with your Confluence Server Instance. We aim for a near-zero configuration experience and handle calendar integration and synchronization on your behalf.

In order to use the full feature set of Meetical you need to

  • Allow communication between your Confluence REST API and app.meetical.io (on port 443) by configuring your firewall accordingly.
  • Alternatively, reach out to support@meetical.io and we can discuss a full on-premise solution allowing you to run the Meetical Sync Service within your firewall on your own infrastructure.

If your instance is reachable from the internet, you are usually fine. If you are behind the firewall, you need to configure a firewall rule and allow access to your Confluence from our Online Service, so we are able to use the Confluence REST API.

Errors you might see if your firewall is too restrictive

  • If during setup you see the message 'Error connecting with Confluence: Server error. Please contact Support.', you might be behind a firewall but your changes are high you can configure a firewall rule in order to make Meetical work.
  • If you do not even see the Meetical log in screen with an error 'app.meetical.io could not be found' you probably are behind a strict firewall.

In the following we will quickly explain our approach as well as discuss advantages and disadvantages

Using a hybrid Server/Cloud approach comes with a few advantages and disadvantages:

Advantages are:

  • On your side you will have nearly zero Configuration. Users Login with their Google or Microsoft Account, grant access to their Calendar and Confluence Account in few easy stetps and you are ready to go!
  • If you would run the Sync Services yourself, you would for example need to create an OAuth Client ID and go through a verification process with Google or Microsoft.
  • Furthermore, we can deploy Improvements and Bugfixes continuously and fast without your need to always update the Confluence App. (However, some bigger updates will still require you to update the App)
  • Moreover, your Confluence Instance Performance is not affected by change tracking and sync load, because we run all change tracking and sync services for you. We use the Confluence REST API to interact with your instance to process updates.

On the other side...

  • ... using our Cloud Services also means you need to give us access to your calendar and confluence systems. To minimize security issues and privacy concerns we both apply modern cryptographic approaches as well as minimize the data we permanently store on our side. In fact, we never store any content like page titles, event dates, attendees etc. on our side. We store all relevant info on your Confluence server, even the ID mapping between events and pages. However, some information we keep in temporary caches and logging and monitoring services.
  • To learn more about our serious approach to security and privacy, head over to our Terms and Conditions and our Privacy Statement.

If using our Cloud Services is still not an option for you, we can offer that you get in contact with us so we can evaluate running the Sync Service on your infrastructure and behind the firewall. Furthermore, if we see increasing interest from the community, we might offer a fully integrated Confluence App as well. 

Thank you for your interest in Meetical and let me know any further questions here or via support@meetical.io