tycho
Guru (not...)
- Joined
- Aug 9, 2011
- Messages
- 652
- Reaction score
- 272
I've installed the Pogoplug.img file on two separate devices -- Dockstar and Pogoplug Mobile/Backup and Sharing model -- and see the following two issues on both devices.
When I initially saw these issues on the Dockstar I chalked them up to fallout from my clumsily replacing 3.2.0-kirkwood-era files in its root-level, boot and /lib/module directories with 3.14.0-kirkwood files. But yesterday I fired up the brand-new, just-delivered Pogoplug V4 A1 01 with the pogo image on a fresh class-10 SD card and I see exactly the same problems.
Issue 1: SSH Server (and SFTP access): although I can access the Pogo (and Dockstar) via Putty just fine, and the Status Screen is "all green" (including Samba, which I just activated)...
... when I bring up the FreePBX System Status page Server Status/SSH Server has a yellow "warn" and mouseover states "SSH Server is not running, you will not be able to connect to the system console remotely."
Curious, and possibly a lie (or perhaps I just don't correctly understand the warning) because Putty works fine.
But, possibly related: I have always -- for years now -- used WinSCP (an SSH/SFTP client) to connect to any PIAF boxrunning on my network, including all previous variants of my Dockstar. WinSCP can't get in to the Pogoplug. It sees it, I authenticate just fine, it says "starting the session..." and then it times out and can't connect. Rather a pain because WinSCP is such a great utility for accessing/changing PIAF box files and this is the first and only time this has happened.. Otherwise I have to halt the Pogo, eject its SD card, and install it in another machine to read/write.
Is SFTP not running on the Pogo or is there anything else to look at/correct that anyone can suggest?
Issue 2: ARI Issue [FIXED]: If I click the "User Panel" button at the top of the FreePBX System Status screen (directing me to http://192.168.2.XXX/recordings/) on a fresh pogoplug.img install (whether on the Pogo or the Dockstar) I get an ARI error:
Perhaps this is by design and I have just missed the discussion in the Pogo-IPBX thread or elsewhere.
In any event, I Googled the issue and came up with some old threads relating to this error message, including some from this forum back in '07 :
Nothing much current, however.
Checking on the applicability of one suggestion, my /etc/hosts file looks like this:
The "main.conf.php" file in /var/www/html/recordings/includes contains this entry:
My /etc/asterisk/manager.conf file looks like this:
So, enabled=yes, and permit=127.0.0.1, as required by the warning language.
Trying one of the other suggestions in the thread above, I ultimately I saved a copy of the original main.conf.php file called main.conf.php.orig, and then edited main.conf.php so as to change every instance of "localhost" to "127.0.0.1". On restart I am again able to click the "User Panel" button at the top of the FreePBX System Status screen and access the VM page.
When I initially saw these issues on the Dockstar I chalked them up to fallout from my clumsily replacing 3.2.0-kirkwood-era files in its root-level, boot and /lib/module directories with 3.14.0-kirkwood files. But yesterday I fired up the brand-new, just-delivered Pogoplug V4 A1 01 with the pogo image on a fresh class-10 SD card and I see exactly the same problems.
Issue 1: SSH Server (and SFTP access): although I can access the Pogo (and Dockstar) via Putty just fine, and the Status Screen is "all green" (including Samba, which I just activated)...
... when I bring up the FreePBX System Status page Server Status/SSH Server has a yellow "warn" and mouseover states "SSH Server is not running, you will not be able to connect to the system console remotely."
Curious, and possibly a lie (or perhaps I just don't correctly understand the warning) because Putty works fine.
But, possibly related: I have always -- for years now -- used WinSCP (an SSH/SFTP client) to connect to any PIAF boxrunning on my network, including all previous variants of my Dockstar. WinSCP can't get in to the Pogoplug. It sees it, I authenticate just fine, it says "starting the session..." and then it times out and can't connect. Rather a pain because WinSCP is such a great utility for accessing/changing PIAF box files and this is the first and only time this has happened.. Otherwise I have to halt the Pogo, eject its SD card, and install it in another machine to read/write.
Is SFTP not running on the Pogo or is there anything else to look at/correct that anyone can suggest?
Issue 2: ARI Issue [FIXED]: If I click the "User Panel" button at the top of the FreePBX System Status screen (directing me to http://192.168.2.XXX/recordings/) on a fresh pogoplug.img install (whether on the Pogo or the Dockstar) I get an ARI error:
Perhaps this is by design and I have just missed the discussion in the Pogo-IPBX thread or elsewhere.
In any event, I Googled the issue and came up with some old threads relating to this error message, including some from this forum back in '07 :
Nothing much current, however.
Checking on the applicability of one suggestion, my /etc/hosts file looks like this:
127.0.0.1pogoplug.incrediblepbx.com localhost
::1pogoplug.incrediblepbx.com localhost ip6-localhost ip6-loopback
fe00::0ip6-localnet
ff00::0ip6-mcastprefix
ff02::1ip6-allnodes
ff02::2ip6-allrouters
That seems compliant with jroper's advice in the above thread (have both localhost and 127.0.0.1 in the hosts file), but the problem persists.The "main.conf.php" file in /var/www/html/recordings/includes contains this entry:
# Host for Asterisk Manager Interface
#
$ASTERISKMGR_DBHOST = "localhost";
My /etc/asterisk/manager.conf file looks like this:
[general]
enabled = yes
port = 5038
bindaddr = 0.0.0.0
displayconnects=no ;only effects 1.6+
[admin]
secret = amp111
deny=0.0.0.0/0.0.0.0
permit=127.0.0.1/255.255.255.0
read = system,call,log,verbose,command,agent,user,config,command,dtmf,reporting,cdr,dialplan,originate
write = system,call,log,verbose,command,agent,user,config,command,dtmf,reporting,cdr,dialplan,originate
writetimeout = 5000
So, enabled=yes, and permit=127.0.0.1, as required by the warning language.
Trying one of the other suggestions in the thread above, I ultimately I saved a copy of the original main.conf.php file called main.conf.php.orig, and then edited main.conf.php so as to change every instance of "localhost" to "127.0.0.1". On restart I am again able to click the "User Panel" button at the top of the FreePBX System Status screen and access the VM page.