R.I.P. Wable: Fun While It Lasted

[w1ve]

I guess the killer is the OpenVZ template at Wable... I'd simply use geoIP if I could.

 

[completetech]

I signed up last night after reading this. I'm impressed with the speed of creating the vm. Here's my question for those who have set up a pbx with this service. I tried using the guide for 2.11 and it failed the file check. I tried 4 separate times. Then I tried 12 with gui. It seemed to go fine except that I can not login through the web portion of the pbx.

If anyone canaybe give me some guidance as far as what they did to get it working I would really appreciate it.

Fyi... there is no centOS 6.5 listed, so I chose centOS 6 minimal

 

[TonyColorado]

I signed up last night after reading this. I'm impressed with the speed of creating the vm. Here's my question for those who have set up a pbx with this service. I tried using the guide for 2.11 and it failed the file check. I tried 4 separate times. Then I tried 12 with gui. It seemed to go fine except that I can not login through the web portion of the pbx.

If anyone canaybe give me some guidance as far as what they did to get it working I would really appreciate it.

Fyi... there is no centOS 6.5 listed, so I chose centOS 6 minimal

Why can't you login? Are you seeing an error, or not even seeing the login page?

FWIW:
I used the "centos-6-x86_64-minimal" distribution and followed the guide here for the 12 gui: http://nerdvittles.com/?p=13599
I did have trouble with the Ubuntu and CentOS7 builds. It sounds like we followed the same guide, but perhaps you selected a different distribution (non 64 bit for example?)

I did this a couple of weeks ago, so perhaps something has changed either with the IPBX installation script or with Wable's distribution. Perhaps someone who has installed more recently can comment?

 

[completetech]

I did follow the same guide for the gui and non. I did choose centOS 6 version you did. The gui one "finished" and I can goto the ip address and choose admin then once trying to login using username of admin and my extremely secure password I created from previous steps in the guide I get invalid credentials everytime

 

[wardmundy]

1. /root/admin-pw-change

2. Login to GUI via web with admin and your new password

 

[completetech]

Yes. And upon doing that it does not work. Also. Tried a few times and even a reboot afterwards. .. I'll try again with a new vm

 

[KUMARULLAL]

I faced the exact same problem as completetech on wable.com when I chose the ubuntu 14.04 64 bit template. It did not install, It got stuck on configuring mysql-server.
Then I decided to use centos5 64 bit templates as suggested by Tonycolorado. It wprked.

 

[KUMARULLAL]

However, because it is openvz container, the voicemail to email still gives me a problem.
I mapped the IP of the vps to vps1.xyz.com. I also assigned the same hostname as vps1.xyz.com
The voicemail notification does to reach gmail email address, but surprisingly, it did send an sms on my cell phone alerting me about a voicemail. The text message did not have any details about the caller ID or duration of message etc.
So I am still stuck. I don't know where am I going wrong. The email notification should work. I dont know what am I doing wrong.

 

[TonyColorado]

However, because it is openvz container, the voicemail to email still gives me a problem.
I mapped the IP of the vps to vps1.xyz.com. I also assigned the same hostname as vps1.xyz.com
The voicemail notification does to reach gmail email address, but surprisingly, it did send an sms on my cell phone alerting me about a voicemail. The text message did not have any details about the caller ID or duration of message etc.
So I am still stuck. I don't know where am I going wrong. The email notification should work. I dont know what am I doing wrong.

I was having this problem with the early builds of the Incredible GUI but it was resolved in the build on June 4th. Steps to fix this are available here: http://pbxinaflash.com/community/in...e-pbx-gui-bugs-fixes.17123/page-5#post-111026
(or, just run a fresh install)

 

[TonyColorado]

Yes. And upon doing that it does not work. Also. Tried a few times and even a reboot afterwards. .. I'll try again with a new vm

So, I spun up another Wable Instance tonight and ran a fresh install. I was able to get everything working.

Here are my steps:

1. I installed the centos-6-x86_64-minimal distro: http://take.ms/9ajIz
2. I enabled eth0. I don't know if this is required, but seems like it couldn't hurt: http://take.ms/cDooZ
3. I followed the tutorial here: http://nerdvittles.com/?p=13599, specifically I
   1. Ran this block of code: http://take.ms/VXjao
   2. Then I logged back in following the reboot and ran this block of code: http://take.ms/gUIUd
   3. Following the installation, I noticed that when I copied and pasted the block of code above the final line "gui-fix" did not run. So, I entered it again (Make sure you do this! This line is important)
4. I then set my admin password: root/admin-pw-change
5. Then, I visited my URL. Page loads! http://take.ms/06EIT
6. Then, I logged in: http://take.ms/5gPpH
7. I made a test call for good measure (just to the internal echo test *43 number) - Worked fine

Hope this helps. Good luck!

 

[completetech]

So I was able to successfully complete a build and install. crazy thing is I was even able to login and check out the new gui and all... Last night that was. Now today I have a bunch of "on Hold" time while onsite for a job and tried to access it and play around some more with it and nothing is accessible. No gui, no SSH. nothing. The only thing I am able to do is in the Wable portal wither reboot, delete the VM or reload the OS.

Submitted a ticket and awaiting feedback from them.

I appreciate all of the help from everyone. Must be that I am just having an odd ball case with this.

Also.... When running the code for Grub, it fails on the first line

sed -i 's|quiet|quiet net.ifnames=0 biosdevdame=0|' /etc/default/grub

and the second line

grub2-mkconfig -o /boot/grub2/grub.cfg

Not sure if that matters or not.

 

[wardmundy]

grub errors don't matter. It doesn't use grub.

 

[wardmundy]

completetech: wable is having some problems. One of our servers got irreparably damaged yesterday. At first, I thought it was some bad guy that had managed to break in, but now I'm not so sure. Attempts to rebuild the VM with a snapshot hung. Attempts to kill the VM and start over hung. If you want a quick, reliable sandbox, I think Digital Ocean is a better choice frankly.

 

[krzykat]

completetech: wable is having some problems. One of our servers got irreparably damaged yesterday. At first, I thought it was some bad guy that had managed to break in, but now I'm not so sure. Attempts to rebuild the VM with a snapshot hung. Attempts to kill the VM and start over hung. If you want a quick, reliable sandbox, I think Digital Ocean is a better choice frankly.

Wow - they seemed so fast and solid. Did you open a support ticket with them? What did they say? I was honestly looking at putting live clients on this.

 

[completetech]

I did submit a ticket asking what was going on. and then since I am "onsite" and also "on hold" for almost 2 hours now waiting to be released to head to the next site. I built another VM and it is working..... for now at least..

We will see. I plan on testing it thoroughly throughout the next few days...

My thought with all of this was to try and be able to quickly deploy systems for customers quickly and at a pricepoint that would appeal to not only me reselling the service/equipment/support but also to the customer.

 

[KUMARULLAL]

OK. Here is something you may try for wable centos 6.x openvz image.
By default, when you spin up any vm from the templates, you get 2 network adaptors, namely venet0 and venet0:0
The venet0 only has the entry of 127.0.0.1 localhost
The real adapter is venet0:0 that has the actual ip addresses assigned to your vm.
The first thing you do, is the go to manage vps and enable eth0/pbx. That will create ifcfg-eth0 and eth0 adapter.
ifcfg-eth0 aslso has the entry of 127.0.0.1 localhost
Leave all as it is. (Don't assign the actual IP address to eth0.)
Next thing is to disable network manager.
Set NM_CONTROLLED=no and stop the Network Manager daemon and prevent it from restarting during boots:
service NetworkManager stop
Then disable network manager on startup
chkconfig NetworkManager off
Finally edit /etc/resolv.conf
and manually add these 2 entries.
nameserver 8.8.8.8
nameserver 8.8.4.4
When you try to restart the network service, your putty session might freeze, so I did a reboot.
Then you can proceed with incrediblepbx install
After that everything work fine.
I have not tried to restore from the snapshot to see if it maintains the system integrity.
Check if this works for you.
Regards

 

[KUMARULLAL]

I can confirm that a new vps created from a snapshot worked for me. Make sure, you leave some disk space (3 to 4 gigs) from the total and leave some ram space. (If your first vps used 1GB and you have a toal of 2GB, then l;eave 512 available)

 

[completetech]

KUMARULLAL I will have to try your above mentioned suggestions for the network card / eth0 settings. I did all of the times use the enable eth0 from their portal/ section

 

[KUMARULLAL]

Try to also disable network manager and manually add the dns entries in resolv.conf and restart. That should do it.

 

[KUMARULLAL]

Please refer to the instructions once again. I have included something that I missed out to mention. One important step before Disabling NetworkManager on centos is to run this command on the terminal
NM_CONTROLLED=no