Building Elastix 4 via RPM Repo
-
@scottalanmiller said:
yum -y install net-tools
its already installed - when I run netstat it shows my internal ip here
cyrus-master
tcp 0 0 100.78xxxxxxxx
But I don't see my public ip in the list -
@dom said:
@scottalanmiller said:
yum -y install net-tools
its already installed - when I run netstat it shows my internal ip here
cyrus-master
tcp 0 0 100.78xxxxxxxx
But I don't see my public ip in the listThat's not at all the output of...
netstat -tulpn -
Something in the installation is incorrect...If i need to change the server name or ip address which file do I do that in? hostfile?
-
@dom said:
Something in the installation is incorrect...If i need to change the server name or ip address which file do I do that in? hostfile?
Hostname is...
vi /etc/hostnameIP Address is changed easiest using a TUI:
nmtui -
What is the output of...
netstat -tulpn -
said:
netstat -tulpn
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.0.1:20004 0.0.0.0:* LISTEN 2553/php
tcp 0 0 0.0.0.0:3306 0.0.0.0:* LISTEN 1841/mysqld
tcp 0 0 0.0.0.0:5038 0.0.0.0:* LISTEN 2519/asterisk
tcp 0 0 0.0.0.0:110 0.0.0.0:* LISTEN 2496/cyrus-master
tcp 0 0 0.0.0.0:143 0.0.0.0:* LISTEN 2496/cyrus-master
tcp 0 0 0.0.0.0:4559 0.0.0.0:* LISTEN 2547/hfaxd
tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 1295/dnsmasq
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1290/sshd
tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 2057/master
tcp 0 0 0.0.0.0:4190 0.0.0.0:* LISTEN 2496/cyrus-master
tcp 0 0 0.0.0.0:993 0.0.0.0:* LISTEN 2496/cyrus-master
tcp 0 0 100.78.250.75:16001 0.0.0.0:* LISTEN 1298/python
tcp 0 0 0.0.0.0:995 0.0.0.0:* LISTEN 2496/cyrus-master
tcp6 0 0 :::110 :::* LISTEN 2496/cyrus-master
tcp6 0 0 :::143 :::* LISTEN 2496/cyrus-master
tcp6 0 0 :::80 :::* LISTEN 3853/httpd
tcp6 0 0 :::53 :::* LISTEN 1295/dnsmasq
tcp6 0 0 :::22 :::* LISTEN 1290/sshd
tcp6 0 0 :::25 :::* LISTEN 2057/master
tcp6 0 0 :::443 :::* LISTEN 3853/httpd
tcp6 0 0 :::4190 :::* LISTEN 2496/cyrus-master
tcp6 0 0 :::993 :::* LISTEN 2496/cyrus-master
tcp6 0 0 :::995 :::* LISTEN 2496/cyrus-master
udp 0 0 0.0.0.0:53 0.0.0.0:* 1295/dnsmasq
udp 0 0 0.0.0.0:68 0.0.0.0:* 3800/dhclient
udp 0 0 0.0.0.0:69 0.0.0.0:* 1303/xinetd
udp 0 0 127.0.0.1:323 0.0.0.0:* 647/chronyd
udp 0 0 0.0.0.0:4520 0.0.0.0:* 2519/asterisk
udp 0 0 0.0.0.0:2727 0.0.0.0:* 2519/asterisk
udp 0 0 0.0.0.0:50631 0.0.0.0:* 3800/dhclient
udp6 0 0 :::53 :::* 1295/dnsmasq
udp6 0 0 ::1:323 :::* 647/chronyd
udp6 0 0 :::53939 :::* 3800/dhclient -
said:
nmtui
BTW should mention that Im using dynamic ip address
internal ip is 100.78.250.75
public dynamic is 40.121.19.1 -
So https://100.78.250.75/ is bringing up the 500 error?
-
Tried both and yes 500 error
-
Do a telnet on the local box and see if it connects.
telnet localhost 80You might need telnet...
yum -y install telnet -
yep it connects
-
@dom said:
yep it connects
Webserver is definitely up. Chrome loaded your IP and complained about the certificate. I then got this result after accepting the certificate
-
Also http://40.121.19.1 redirects to https://40.121.19.1
-
Did you add an HTTP to HTTPS redirect before getting things working?
-
@scottalanmiller said:
Did you add an HTTP to HTTPS redirect before getting things working?
Elastix does that by default. Always has.
-
@JaredBusch said:
@scottalanmiller said:
Did you add an HTTP to HTTPS redirect before getting things working?
Elastix does that by default. Always has.
Doh. That's right.
-
Azure provides the following:
DNS NAME
pbx77.cloudapp.net
HOST NAME
pbx77
PUBLIC VIRTUAL IP (VIP) ADDRESS
40.121.19.1
INTERNAL IP ADDRESS
100.78.254.76
I access the site and I ssh in using the public vip. When Elastix setup it says:
To access your Elastix System, using a separate workstation (PC/MAC/Linux)
Open the Internet Browser using the following URL:
http://100.78.254.76After the install I did'nt change anything - which files (conf? host?) can I look at to trouble shoot this?
-
Viewing the page source shows your site returning blank.
As this is connecting the ports must be open. But just double check that you've opened the right ports on Azure for this as you have two separate firewalls to deal with here. Azure's firewall is unrelated to the VM's firewall.
-
I opened up the standard ports on azure 80 443 and 22 and the same on centos
firewall-cmd --zone=public --query-port=443/tcp
yes
firewall-cmd --zone=public --query-port=80/tcp
yes -
Okay, just wanted to be sure. I assumed from the error, but better safe than sorry.
