Hi Bertie
Many thanks for update and kudos to IW.
I am sure you have, but have you fully restarted server and cleared your browser cache
I will check later today to see what I bring up in browser for you
Many thanks
John
Hi Bertie
I have just checked on one of our servers, and if I understand correctly, you have set your IP address for 80 and 443
Please could you edit them and just set as
/etc/httpd/conf/httpd.conf
Listen 80
/etc/httpd/conf.d/ssl.conf
Listen 443
service iworx stop
service iworx start
service httpd stop
service httpd start
clear your browser cache and test
Many thanks
John
Hi Bertie
Many thanks
I am not sure why you have differnt IP shown for listen, as I just checked on one of our servers with multiple IP, and we have not explicitly included them, just set global for listen to 80 and 443 in respective files
Apache will complain if you have global listen 80 and defined IP to listen to I think from memory, or it could be some vhost files are explicitly defined for listen ip ports perhaps
This is why direct access to server helps, as it can be checked quickly
You could also just try hashing out all listen on all IP, and uncomment Listen 80, same with ssl.conf, then stop/start apache and test
Have you reopened your ticket with IW, so they can have a look
Many thanks
John
Hi Bertie
Many thanks
IW rock but I do not know who your reseller is sorry. I do not work for IW or have any access to any data
If you check the 2 servers which are working as expected, is there any difference to those 2 conf files
I am sure your reseller will reply or IW may well reply, but there is a set procedure to go through before IW directly can help. Also, please understand IW start work at USA time, which uk is about 5 - 7 hours in front of USA
Many thanks
John
The other option is just disabling port 2080 on Interworx Apache so no one can connect insecurely in the first place.