Building Elastix MT via RPM Repo
-
@scottalanmiller Oh, I see, activate a fw accept to see if the problem was, and this is resolved, I never imagined that the default was fw reject all connections, but now I can enter the dashboard, scoot thanks for your help
Scritp for fw-accept.
#!bin/bash
iptables -F
iptables -X
iptables -t nat -F
iptables -t nat -X
iptables -t mangle -F
iptables -t mangle -X
iptables -P INPUT ACCEPT
iptables -P FORWARD ACCEPT
iptables -P OUTPUT ACCEPT -
@zathiro said:
@scottalanmiller Oh, I see, activate a fw accept to see if the problem was, and this is resolved, I never imagined that the default was fw reject all connections, but now I can enter the dashboard, scoot thanks for your help
Scritp for fw-accept.
#!bin/bash
iptables -F
iptables -X
iptables -t nat -F
iptables -t nat -X
iptables -t mangle -F
iptables -t mangle -X
iptables -P INPUT ACCEPT
iptables -P FORWARD ACCEPT
iptables -P OUTPUT ACCEPTYes, the default is to accept nothing but port 22, which is the SSH port for management. This is the industry standard (that Linux started.) Every OS blocks everything by default now on the firewall. Having the web open by default would be very bad. But rather easy to open up when needed.
-
@scottalanmiller Yes off course, now I can open ports only for my vpn network that I have and not for the public
-
All working now?
-
@scottalanmiller Yes! now it working and performance the firewall with iptables, thanks scott, for all!!
-
No problem. Glad that we got that fixed. I'll update the doc to mention that. Firewall is default on in CentOS 6 so I had ignored it.
-
@scottalanmiller Yes!, I also ignored the firewall of centos
-
I am trying to install an copy of Elastix MT on a VPS on ImpactVPS. I got this part and got this. Can you let me know what I'm doing wrong? [root@ElastixServer ~]# cd /mnt/elastixmt/Elastix
-bash: cd: /mnt/elastixmt/Elastix: No such file or directory -
@VoipNewbie said in Building Elastix MT via RPM Repo:
I am trying to install an copy of Elastix MT on a VPS on ImpactVPS. I got this part and got this. Can you let me know what I'm doing wrong? [root@ElastixServer ~]# cd /mnt/elastixmt/Elastix
-bash: cd: /mnt/elastixmt/Elastix: No such file or directoryIn order to navigate to that you need to have uploaded the ISO image and mounted it using that name. What did you do before this step?
-
@scottalanmiller I was following your tutorial. Hy4y? Above.
-
@scottalanmiller I was following your Elastix MT tutorial. The one you posted above.
-
@scottalanmiller this is the tutorial I was following.
#!/bin/bash
SAM's Elastix MT on CentOS 6 Installation and Build Script
http://mangolassi.it/topic/6243/building-elastix-mt-via-rpm-repo
Report any issues or questions on that thread.
yum -y install epel-release
yum -y install fail2ban htop sysstat glances wget screen
yum -y update
cd /tmp
wget http://sourceforge.net/projects/elastix/files/Elastix PBX Appliance Software/3.0.0/latest/Elastix-3.0.0-Stable-x86_64-bin-10nov2014.iso/download
mv download elastixmt.iso
mkdir -p /mnt/elastixmt
mount -o loop /tmp/elastixmt.iso /mnt/elastixmt
cat > /etc/yum.repos.d/Elastix.repo <<EOF
[Elastix-cd]
name=Elastix-cd
baseurl=file:///mnt/elastixmt/
gpgcheck=0
enabled=1
EOF
cd /mnt/elastixmt/Elastix
for i in $(ls); do yum -y install $i; done
for i in $(ls); do yum -y install $i; done
/etc/init.d/mysqld start
/etc/init.d/elastix-firstboot start && reboot -
That suggests that one of these two lines failed when you ran it. Did you get an error message?
mkdir -p /mnt/elastixmt mount -o loop /tmp/elastixmt.iso /mnt/elastixmtIf you do a df -h we should see if it is mounted or not.
-
@scottalanmiller Thanks for the script! I was able to install Elastix MT on a cloud server from Digital Ocean running CentOS 6.8 64-bit. I am having an issue and I was wondering if you could help me. I am trying to configure the server, and the first step I usually do is set up the Email > Remote SMTP. I usually use a gmail account, but I am getting an error saying that it "Failed to send hello command" and it won't let me keep the status to ON. I am at a loss... Do you have some light you can shed to this? Thank you in advance for your time and response.
P.S > I think the script ran successfully, but I got a lot of "Missing; Nothing to do" messages when running the "for i in $(ls); do yum -y install $i; done" commands. In fact, the second time I ran it, it was all about those messages. Nothing really installed. The first time around, it downloaded and ran many items.
-
@bgiacaman welcome to the community!
-
@bgiacaman said in Building Elastix MT via RPM Repo:
@scottalanmiller Thanks for the script! I was able to install Elastix MT on a cloud server from Digital Ocean running CentOS 6.8 64-bit. I am having an issue and I was wondering if you could help me. I am trying to configure the server, and the first step I usually do is set up the Email > Remote SMTP. I usually use a gmail account, but I am getting an error saying that it "Failed to send hello command" and it won't let me keep the status to ON. I am at a loss... Do you have some light you can shed to this? Thank you in advance for your time and response.
P.S > I think the script ran successfully, but I got a lot of "Missing; Nothing to do" messages when running the "for i in $(ls); do yum -y install $i; done" commands. In fact, the second time I ran it, it was all about those messages. Nothing really installed. The first time around, it downloaded and ran many items.
Start by testing with mailx. Try this...
yum -y install mailxThen try sending yourself something...
mail -s "This is a test" [email protected] < sometextfile -
@scottalanmiller Thanks for the quick reply! Tried it and it sent me an email (although went straight to my junk folder). Email came from [email protected].
-
@bgiacaman said in Building Elastix MT via RPM Repo:
@scottalanmiller Thanks for the quick reply! Tried it and it sent me an email (although went straight to my junk folder). Email came from [email protected].
OKay, so the email subsystem is working. That's the first thing. Now... where could the break be after that.....
-
@scottalanmiller Maybe firewall rules?
-
You can turn off the firewall to be sure, but no, not realistically. Firewall would not cause that error nor would it impact outgoing SMTP by default.
