#1 2020-08-28 01:55:44

Marius S.

[SOLVED] [10.5] Not redirecting automatically from http to https

Hello,

We have installed Adobe Connect 10.5 on new server and migrated all recordings, users, etc. from our old 9.6 version.
We have installed Stunnel and ACTS, enabled SSL. Adobe Connect works just fine, you can enter room using browser or Application.

However I noticed that now if we try to open our Adobe Connect in browser by entering http://..... it doesn't work.
If we enter https://.... it works.

So somehow http is not redirecting to https automatically.

What might be the problem? Is this might be Windows Server 2016 settings? Or we missed something in Adobe Connect settings/config files?

Thanks.

Last edited by Marius S. (2020-10-12 01:08:39)

Jorma_at_CoSo

Re: [SOLVED] [10.5] Not redirecting automatically from http to https

Did you add the following to the custom.ini file after installing 10.5?

ADMIN_PROTOCOL=https://
SSL_ONLY=yes

---

CoSo Cloud
Adobe Certified Instructor

Marius S.

Re: [SOLVED] [10.5] Not redirecting automatically from http to https

Hello Jorma,

Yes we have these two lines in custom.ini file.
Also we have this line for ACTS as we installed it on the same server: ACTS_PROTOCOL=wss:443

But if we manually enter https://ouradobe.com/room and it opens so this means that Stunnel is configured properly?

For configuring Stunnel we used this manual: https://blogs.adobe.com/connectsupport/files/2016/04/Connect-SSL-Guide.pdf
"Application and Meeting server SSL".
Also we have added these lines for stunnel.conf for ACTS: https://blogs.adobe.com/connectsupport/adobe-connect-10-1-switch-the-default-acts-service-protocol-from-ws-to-wss/

Maybe we need to check something on Windows Server 2016 level?
Because we installed new Windows server on VM, imported database, installed 10.5, copied content folder with recordings.
I am not sure maybe we need to add http>https redirect on Windows server settings?

Thanks.

Marius S.

Re: [SOLVED] [10.5] Not redirecting automatically from http to https

We still did not solve the issue.
Adobe Connect support advised to try generate SSL certificate which would have "Domain – Intermediate – Root" chain.
Because using ssllabs.com/ssltest it was showing "This server's certificate chain is incomplete".

We got SSL certificate with Domain – Intermediate – Root, ssllabs.com test was not showing error about chain, however Adobe Connect still did not redirect from http to https.
I tried change extension from .cer to .crt, to .pem, but still did not work.

Thanks.

Jorma_at_CoSo

Re: [SOLVED] [10.5] Not redirecting automatically from http to https

This should be a function of the load balancer or SSL packager you are using. Here's a Google help page explaining how this works.

https://cloud.google.com/load-balancing … s-redirect

---

CoSo Cloud
Adobe Certified Instructor

Marius S.

Re: [SOLVED] [10.5] Not redirecting automatically from http to https

This should be a function of the load balancer or SSL packager you are using. Here's a Google help page explaining how this works.

https://cloud.google.com/load-balancing … s-redirect

Hello Jorma, we are using Stunnel and we have one server and not using load balancer.

We have SSL certificate for ACTS (acts.ac.xxxxxxx.com), so it's a sub-subdomain and we use wildcard SSL certificate for that.
I have read that wildcards are working only for subdomain, not for sub-subdomains.
But I don't think this could be a problem because when we open ac.xxxxxxx.com so ACTS doesn't even activated as it's just main page of Adobe Connect.

Also if I am connected to Windows Server 2016 using RDP and inside server I open browser and enter http://ac.xxxxxxx.com it automatically redirects to https.

Jorma_at_CoSo

Re: [SOLVED] [10.5] Not redirecting automatically from http to https

This sounds like it may be a firewall setting on the server. Does the server allow inbound requests on port 80 and 443?

---

CoSo Cloud
Adobe Certified Instructor

Marius S.

Re: [SOLVED] [10.5] Not redirecting automatically from http to https

Hello Jorma, yes this was the issue. We needed to add inbound rule in firewall settings for 80 port to be open.
It is working now.