Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Cannot Bind Interface to 80
#1
Trying to figure out what is causing these errors in the logs. Recent change was adding SSL.

These errors are coming from the CQCWebSrv process.

Quote:Could not initialize listener engine on port 80.

Could not bind any listening interfaces on 80
Reply
#2
Something else is using port 80. Commonly it might be some default installation of IIS or something like that. You can find that thing and turn it off, or change the non-secure port that CQC uses (and just indicate the port in the URL.)
Dean Roddey
Explorans limites defectum
Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  Check Box widget on WebRIVA vs Interface Viewer bryanb 1 423 04-23-2020, 06:15 AM
Last Post: bryanb
  Problem with Accesssing Variables Driver Client Interface kblagron 5 970 03-05-2020, 02:24 PM
Last Post: kblagron
  Simple device control from Admin Interface simplextech 7 1,550 01-04-2020, 12:18 PM
Last Post: simplextech
  Pause / Resume Triggered or Scheduled Actions from the Interface Viewer gReatAutomation 2 991 10-30-2019, 01:38 PM
Last Post: gReatAutomation
  Serialization of CQC SMS Serial Interface Driver gReatAutomation 52 9,101 09-21-2019, 12:59 PM
Last Post: gReatAutomation
  SOLVED: VLC dll Issues with CQC Interface Template Viewer gReatAutomation 3 1,332 06-17-2019, 06:17 AM
Last Post: gReatAutomation
  ELK M1 Client Interface question lleo 1 822 06-12-2019, 08:15 AM
Last Post: Dean Roddey
  Admin interface and CML IDE interface issue lleo 5 1,973 01-11-2019, 03:07 PM
Last Post: Dean Roddey
  Elk Client Interface Gremlins IVB 9 2,091 12-23-2018, 08:58 PM
Last Post: IVB
  Copy and Paste into Global Cache Client Interface kblagron 3 1,559 11-01-2018, 02:23 PM
Last Post: kblagron

Forum Jump:


Users browsing this thread: 1 Guest(s)