Thanks,

I had already managed to set the FOPRUN=false but had not stopped it afterwards!!!

So that fixed the issue

:D

Hi FOP2 has been working great for months then today suddenly it stops, ran yum updates and freepbx updates (Using Elastix 2)

Getting this:
[root@elastixv2 fop2]# /usr/local/fop2/fop2_server --test
/usr/local/fop2/autoconfig-buttons-freepbx.sh: line 15: [: too many arguments
Connection to manager OK!

but its saying that its connection to the manager is OK

and this

[root@elastixv2 fop2]# netstat -lnp | grep 444
tcp 0 0 0.0.0.0:4445 0.0.0.0:* LISTEN 3044/perl

which i fear is the problem as 4445 should be fop2 not perl but if that is the case how did this change happen and how can i correct it? this happened before any updates were done too

Thanks
Robert

OK looks like its fixed after taking out the linux box acting as a router and putting in a 'proper' router things are back and working :D :D

Hi

No i am trying to access it from the LAN or via VPN which used to work now for some reason it just wont connect any more even though it shows the server is running

I had installed FOP2 on elastix v2 and bought the license and it was working very well, in the office is a server running mandrake linux acting as a firewall etc, the old IT guy was fired and they didnt have the password for this machine so we managed to reset the password and removed some of the firewall rules such as port 22 access there was no rule for port 4445 or anything but now we can no longer login to FOP2 i have tried adding firewall rules but to no avail i cant get to it via the LAN or via VPN i get the login box but no further any ideas as im stuck!

Thanks