Another option is to disable websockets in Firefox itself, go to:

about:config

and set:

network.websocket.enabled = false

Anyways, I will release FOP 2.26 probably at the end of this week that will fix websockets for firefox 11.

Nicolas,

I update to version 2.26 now and had the same problem in firefox 11.
Only disabling websocket it worked.

FOP 2.26 It works fine in Firefox 11. Perhaps you forgot to restart the fop2 server.

/usr/local/fop2/fop2_server -v

Are you on 2.26?

All I can say: it works for me using Firefox 11. It should work for you.

Running in the command line does not mean that the running server is that version, you can have a previous version running, download the new version and upgrade (and by not restarting the service, keep the old version running).

I am not saying that this is the case, but could be. And as I said before, it works for me and for several other users using Firefox 11. I am sorry if it does not work for you.

Best regards,

if you get the login prompt, enter credentials, and you get it the prompt one more time, then it is working but you are supplying incorrect credentials. In that case be sure you updated fop2admin because the new autoconfig scripts depends on the latest fop2admin version.

To anyone having problems with firefox 11, please catch me on the live help and provide me access to your panel so I can try myself. If I cannot reproduce a problem, there is no problem.

Just a note of warning to Firefox 11 users that load the panel via https, in order to get it to work with fop2 and websockets, you must set in about:config

network.websocket.allowInsecureFromHTTPS = true

This is not needed if you load fop2 via http, only when using Firefox 11 and fop2 over https.

Please be sure to clear temporary internet files or flush the cache when upgrading. If your browser has the old fop2.js file or index.html file, it will fail to load exactly as many of you are describing.

If you have issues, please look at all steps in this online troubleshooter:

http://support.asternic.biz/index.php?/ ... tep/View/4

Cache cleared, troubleshooter did not help. Still the same problem.
Firefox 11 works. IE 9 32bit on Win7 64bit and IE 8 on Win XP not works. :?:

For Internet Explorer you need Adobe Flash installed and working (not disabled). Be sure adobe flash works.
IE never had issues as it always needed Adobe Flash plugin, while Chrome and Firefox are ahead of the curve and are actively implementing html5 websockets insteqad. Remember also that you should ALLOW access to tcp port 4445, if you have any firewall in those windows machines, you must allow that connection or disable the firewall.

If you want you can catch me in the live help, and if you can provide access to your box I can tell you if *I* have problems connecting to your fop2 install.

Just upgraded my FOP2 server today to 2.26.

Couldn't login with firefox or IE. Login just cycles after entering. Cleared cache as advised on earlier posts.

The httpd logfile states the following:

[Wed Apr 04 00:25:09 2012] [error] [client 10.100.100.25] File does not exist: /var/www/html/fop2/fop2-variablesLAW.txt, referer: http://10.100.100.19/fop2/?context=law

It looks like the variables file wasn't being created. Deleted the entire /usr/local/fop2 directory as well as /var/www/html/fop2 and reloaded.

Cfg file is

[law]
user=7400:7400:dial,transfer,pickup
buttonfile=law_buttons.cfg

Any thoughts? I went through the troubleshooter and everything seemed like it was working.

The .txt file is not a requirement, that error is normal.

Again, there is not much to check, but what you have to check is most probably OUTSIDE the fop2 configuration.

I cannot write a guide on how to configure/enable/disable personal antivirus/firewalls on Windows Machines. One common reason is to have such a tool installed, and that tools prevents/stops the connection from your desktop machine to the fop2 server on port 4445.

Also, a network firewall or firewall rules on the asterisk server itself might prevent connections to that port.

Also, you must verify that fop2 server is running AND BINDINDG to that port.

If your fop2 server is behind a router/nat, you must port forward and allow tcp port 4445.

If *every* browser fails, then something of the above is occuring, and most of that is network/security configuration, outside of fop2 itself.