Using Mattermost and GitLab Omnibus on one server without Domain

How to Use GitLab
1

Hi all,

i installed a GitLab instance on a Redhat 7 using yum.
I do not have a Domain, so i set the IP adress als external_url:

Blockquote
external_url ‘http://xx.xxx.xxx.xxx’

GitLab works fine, wenn i access the IP-Address i get my projects listed.

As for mattermost, all i did was to set the mattermost_external_url in gitlab.rb in the same way
to the same IP:

Blockquote
mattermost_external_url ‘http://xx.xxx.xxx.xxx’

and then i ran

Blockquote
sudo gitlab-ctl reconfigure

As far as i understand the docs, this should be suffucient for mattermost to be available.
According to htop mattermost is running.
I expected mattermost to be available at ‘http://xx.xxx.xxx.xxx:8065’,
however i get an ERR_CONNECTION_TIMED_OUT.

Do i have to do anything to access mattermost? (i have not used it ever before)
Is it even possible to run Gitlab and Mattermost on the same machine without using a domain?

Any help is appreciated.

2

Can some please point me into a direction?

3

What system did you install mattermost on? If also on RHEL, did you make sure that the firewall was disabled, or that you created a firewall rule to unblock port 8065?

You can verify this with:

telnet x.x.x.x 8065

if it connects, then a firewall is not blocking it. If no connection, then it would mean that it’s not unblocked. Assuming RHEL7 or higher:

firewall-cmd --add-port 8065/tcp --permanent
firewall-cmd --reload

on the server where mattermost is installed.

1 Like
4

At first the firewall-cmd commands gave me an Error:

FirewallD is not running

However after invoking

firewall-cmd

the commands

firewall-cmd --add-port 8065/tcp --permanent
firewall-cmd --reload

reported a success.

However the telnet invokation still gives me

telnet: connect to address xx.xxx.xxx.xxx : Connection refused

I assume there is some other firewall running (i did not configure this server),
so i will write again, when i managed to unblock the port somehow.

5

If the servers are in the same subnet, then it could be another firewall running on this machine, if not nftables, maybe iptables. If a different subnet, then it could be a firewall between the two networks, so in that case it wouldn’t necessarily be something running on the server itself. But whoever set up the server should be able to help sort out the access where necessary so that the port is unblocked.

1 Like
6

I can access mattermost via 127.0.0.1:8065 when connected to the server,
so I guess this port access is really the issue.
I will have someone with deeper firewall knowledge look into it.

Thanks a lot!

7

Get them to check that port 8065 is not only just bound to localhost (127.0.0.1) but also to the IP of the machine itself. Maybe they need to fix the configuration of Mattermost so that the port is accessible via the IP of the server.