Skip to main content
Announcements
Qlik Connect 2024! Seize endless possibilities! LEARN MORE
cancel
Showing results for 
Search instead for 
Did you mean: 
exfosteve
Partner - Contributor III
Partner - Contributor III

443 port conflict

I'm running qlikview server 12.2 and and running apache on the same server (running on 80 and 443).  I've mapped the qlikview web port to 8080, but there's also a component starting up on 443.  I couldn't find a place to remap this through the management console.

Where can I map this to another port (8443), and what impacts would be there be. 

Thanks,

C:\Windows\system32> netsh http show servicestate

Server session ID: FE0000182000482A

    Version: 2.0

    State: Active

    Properties:

        Max bandwidth: 4294967295

        Timeouts:

Entity body timeout (secs): 120

Drain entity body timeout (secs): 120

Request queue timeout (secs): 120

Idle connection timeout (secs): 120

Header wait timeout (secs): 120

Minimum send rate (bytes/sec): 150

    URL groups:

    URL group ID: FC00001840000001

        State: Active

        Request queue name: Request queue is unnamed.

        Properties:

Max bandwidth: inherited

Max connections: inherited

Timeouts:

Timeout values inherited

Number of registered URLs: 6

Registered URLs:

HTTP://+:8080/QVDESKTOP/

HTTP://+:8080/SCRIPTS/

HTTPS://+:443/SCRIPTS/

HTTP://+:8080/QVPLUGIN/

HTTP://+:8080/QLIKVIEW/

HTTP://+:8080/QVAJAXZFC/

1 Solution

Accepted Solutions
Miguel_Angel_Baeyens

I cannot say in 12.20 but in 12.10 that's the tunnelling DLL used to fall back from QVP to HTTP when QVP is not possible.

Also, this must be something specific to 12.20, since I have it running under 80 (I'm not port forwarding any service or folder).

Contact Qlik Support to see why that 443 is enabled.

View solution in original post

2 Replies
Miguel_Angel_Baeyens

I cannot say in 12.20 but in 12.10 that's the tunnelling DLL used to fall back from QVP to HTTP when QVP is not possible.

Also, this must be something specific to 12.20, since I have it running under 80 (I'm not port forwarding any service or folder).

Contact Qlik Support to see why that 443 is enabled.

exfosteve
Partner - Contributor III
Partner - Contributor III
Author

I ended up getting in touch with qlik support.  I got the HTTPS set up with 000002484 from the support site.   I ended up dropping apache and using the qlikview web server instead.  I had to migrate the users to a custom directory for login purposes.  Still trying to figure out how to get my custom login page working with the new setup.