Again : Connect attempt from '127.0.0.1' unable to authenticate
Submitted by HyperBlade on Mon, 03/31/2008 - 6:27am.
I already read this : http://lists.digium.com/pipermail/asterisk-users/2007-March/18171...
However both my manager.conf and op_server.cfg match :
manager.conf :
[general]
enabled = yes
port = 5038
bindaddr = 0.0.0.0
[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
write = system,call,log,verbose,command,agent,user
op_server.cfg :
[general]
; host or ip address of asterisk
manager_host=127.0.0.1
; user and secret for connecting to * manager
manager_user=admin
manager_secret=amp111
...
also from amportal.conf :
# AMPMGRUSER: the user to access the Asterisk manager interface
AMPMGRUSER=admin
# AMPMGRPASS: the password for AMPMGRUSER
AMPMGRPASS=amp111
AUTHTYPE=none
Does anyone have any idea why I still get the
Parsing '/etc/asterisk/manager.conf': [Mar 31 09:29:16] Found
Connect attempt from '127.0.0.1' unable to authenticate
messages ?
Yes
First of all, shutdown
Wed, 04/09/2008 - 1:23pm
Yes
First of all, shutdown hudlite to see if the message disappear (just to see if it's the same problem as me) :
service hudlite-server stop
If the message disappeared go in trixbox's Asterisk->Config Edit and verify that manager.conf, manager_additionnal.conf or manager_custom.conf have the following entry :
[remote_mgr]
secret=0chanc3yo
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
write=system,call,log,verbose,command,agent,user
save the .conf
apply the changes and restart hudlite : service hudlite-server start
The error message should be gone.
Ah one more thing : if you don't have manager_additionnal.conf and manager_custom.conf, I suggest you create them even if you leave them empty (make sure the owner/group is asterisk).
Hope it helps :)
Just post back if you need more help.
Thanks !
I just rebooted
Wed, 04/09/2008 - 4:47pm
Thanks !
I just rebooted the system and I think I got rid of it. I'll definitely seek your help once the ghostly error comes to haunt my box again.
"Connect attempt from '127.0.0.1' unable to authenticate"
All tricks apart but is there a way we can find out directly what is trying to connect and being rejected ? I've seen several trixbox posts and every time there was a different reason causing the error.
I'm sure the above error message that comes up is a very general one but there can be multiple reasons causing it.
Sorry I was kinda busy
Mon, 04/14/2008 - 7:01am
Sorry I was kinda busy lately.
@zildia143
Did you try what I posted about hudlite ?
Connect attempt from '127.0.0.1' unable to authenticate means that a program on your trixbox/asterisk machine is trying to connect to another program on the same machine but doesn't have the good username/password (or in the case of hudlite, the user ismply didn't exist). If fixing hudlite didn't solve your problem, you'll have to try shutting other programs to find which one is causing trouble. It's probably something like mysql or apache.
BTW I'm no expert on trixbox or asterisk. I just started using it 3 weeks ago (I had 0 knowledge about PBX) so don't be too hard on me if I don't have the answer for you ;)
I found problem!
Thu, 04/24/2008 - 10:28am
did you try search
Fri, 07/11/2008 - 9:31am
Member Since:
2008-03-26