<![CDATA[Login Timeout]]>Hi all.
I've recently installed FOP2 version 2.26 for a 64bit CentOS (fop2-2.26-centos5-x86_64.tgz)
This server has a FreePBX installation, but I cannot login. The login screen appears very well, but when I introduce any extension, regardless if the password is right or wrong I always get the "One moment please" and after 16 connection to the server retries I get the "System is not available right now". I followed all the steps from the setup guide.
If I run "./fop2_server --debug 9" I can see al the messages between FOP2 and Asterisk via AMI. I can see the retrieval of all extensions states, even the SIP trunks:

Flash Operator Panel 2 - No valid license found. Demo Mode

** MANAGER CONNECTION Connecting to localhost:5038 (Server 0)
** MANAGER CONNECTION Connected to localhost:5038 (Server 0)

127.0.0.1 <- Asterisk Call Manager/1.1
127.0.0.1 <- Response: Success
127.0.0.1 <- Challenge: 469955471
127.0.0.1 <- Server: 0

127.0.0.1 <- Response: Success
127.0.0.1 <- Message: Authentication accepted
127.0.0.1 <- Server: 0

127.0.0.1 <- Event: FullyBooted
127.0.0.1 <- Privilege: system,all
127.0.0.1 <- Status: Fully Booted
127.0.0.1 <- Server: 0

127.0.0.1 <- Response: Success
127.0.0.1 <- ActionID: getvar!coresettings
127.0.0.1 <- AMIversion: 1.1
127.0.0.1 <- AsteriskVersion: 1.8.15.0
127.0.0.1 <- SystemName:
127.0.0.1 <- CoreMaxCalls: 0
127.0.0.1 <- CoreMaxLoadAvg: 0.000000
127.0.0.1 <- CoreRunUser:
127.0.0.1 <- CoreRunGroup:
127.0.0.1 <- CoreMaxFilehandles: 0
127.0.0.1 <- CoreRealTimeEnabled: Yes
127.0.0.1 <- CoreCDRenabled: Yes
127.0.0.1 <- CoreHTTPenabled: No
127.0.0.1 <- Server: 0

127.0.0.1 <- Response: Success
127.0.0.1 <- Message: Mailbox Status
127.0.0.1 <- Mailbox: 26109@default
127.0.0.1 <- Waiting: 0
127.0.0.1 <- Server: 0

127.0.0.1 <- Response: Success
127.0.0.1 <- Message: Mailbox Message Count
127.0.0.1 <- Mailbox: 26109@default
127.0.0.1 <- UrgMessages: 0
127.0.0.1 <- NewMessages: 0
127.0.0.1 <- OldMessages: 0
127.0.0.1 <- Server: 0

127.0.0.1 <- Response: Success
127.0.0.1 <- Message: Channel status will follow
127.0.0.1 <- Server: 0

127.0.0.1 <- Event: PeerEntry
127.0.0.1 <- Channeltype: SIP
127.0.0.1 <- ObjectName: mitel-in
127.0.0.1 <- ChanObjectType: peer
127.0.0.1 <- IPaddress: 10.217.115.2
127.0.0.1 <- IPport: 5060
127.0.0.1 <- Dynamic: no
127.0.0.1 <- Forcerport: yes
127.0.0.1 <- VideoSupport: yes
127.0.0.1 <- TextSupport: no
127.0.0.1 <- ACL: no
127.0.0.1 <- Status: OK (13 ms)
127.0.0.1 <- RealtimeDevice: no
127.0.0.1 <- Server: 0

127.0.0.1 <- Event: PeerlistComplete
127.0.0.1 <- EventList: Complete
127.0.0.1 <- ListItems: 1336
127.0.0.1 <- Server: 0

127.0.0.1 <- Response: Success
127.0.0.1 <- EventList: start
127.0.0.1 <- Message: Peer status list will follow
127.0.0.1 <- Server: 0

Response: Success
EventList: start
Message: Peer status list will follow
Server: 0

127.0.0.1 <- Event: PeerlistComplete
127.0.0.1 <- EventList: Complete
127.0.0.1 <- ListItems: 0
127.0.0.1 <- Server: 0

127.0.0.1 <- Response: Success
127.0.0.1 <- Message: Parked calls will follow
127.0.0.1 <- Server: 0

Response: Success
Message: Parked calls will follow
Server: 0

127.0.0.1 <- Event: ParkedCallsComplete
127.0.0.1 <- Total: 0
127.0.0.1 <- Server: 0

127.0.0.1 <- Response: Follows
127.0.0.1 <- Privilege: Command
127.0.0.1 <- ActionID: fop2state
127.0.0.1 <- 0 results found.
127.0.0.1 <- --END COMMAND--
127.0.0.1 <- Server: 0

127.0.0.1 <- Response: Follows
127.0.0.1 <- Privilege: Command
127.0.0.1 <- ActionID: fop2notes
127.0.0.1 <- 0 results found.
127.0.0.1 <- --END COMMAND--
127.0.0.1 <- Server: 0

Do you know any hint?

]]>https://forum.fop2.com/topic/1367/login-timeoutRSS for NodeTue, 27 Oct 2026 19:04:06 GMTTue, 29 Jan 2013 16:50:11 GMT60<![CDATA[Reply to Login Timeout on Wed, 06 Feb 2013 12:52:15 GMT]]>Port 4445 is probably not open or redirected. Your log does not show any traffic from server to client (you must debug client to fop2 server connections, not server to ami connections).

For a web client to connect, it requires access to port tcp/4445, either via websockets or flash xmlsockets. So, be sure that port is open/redirected, and try with different browsers.

Best regards,

]]>https://forum.fop2.com/post/6030https://forum.fop2.com/post/6030Wed, 06 Feb 2013 12:52:15 GMT