# Issue with Inline Frame after Enabling SSL **URL:** \ **Category:** Ignition\ **Tags:** ignition81, perspective\ **Created:** [April 10, 2024, 9:59pm UTC](https://forum.inductiveautomation.com/t/issue-with-inline-frame-after-enabling-ssl/88666 "2024-04-10T21:59:22Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![Eagel007](https://avatars.discourse-cdn.com/v4/letter/e/7bcc69/32.png) [@Eagel007](https://forum.inductiveautomation.com/u/Eagel007)\ **Post date:** [April 10, 2024, 9:59pm UTC](https://forum.inductiveautomation.com/t/issue-with-inline-frame-after-enabling-ssl/88666/1 "2024-04-10T21:59:22Z")
Hi Team, I just installed SSL, everything is fine. But for some reason inline view is not viewing me pdf documents I have on IIS. Is it redirecting? i can ping the address . Wondering if its due to Force redirect of all http. Thanks ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [April 10, 2024, 10:06pm UTC](https://forum.inductiveautomation.com/t/issue-with-inline-frame-after-enabling-ssl/88666/2 "2024-04-10T22:06:02Z")
If you have SSL/TLS enabled on Ignition you must also have it enabled on the IIS server that is hosting the PDFs. ---
**Author:** ![Eagel007](https://avatars.discourse-cdn.com/v4/letter/e/7bcc69/32.png) [@Eagel007](https://forum.inductiveautomation.com/u/Eagel007)\ **Post date:** [April 10, 2024, 10:10pm UTC](https://forum.inductiveautomation.com/t/issue-with-inline-frame-after-enabling-ssl/88666/3 "2024-04-10T22:10:00Z")
even if I disable force redirect? ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [April 10, 2024, 10:11pm UTC](https://forum.inductiveautomation.com/t/issue-with-inline-frame-after-enabling-ssl/88666/4 "2024-04-10T22:11:39Z")
Force redirect isn't relevant here; what that does is force redirect anybody who visits the Ignition Gateway at an HTTP address to the HTTPS address. What you're trying to do is embed non-secure content into an inline frame hosted at a secured addressed. This is called "mixed content" and browsers generally do not allow it. It's not Ignition preventing this, it's your browser. ---
**Author:** ![Eagel007](https://avatars.discourse-cdn.com/v4/letter/e/7bcc69/32.png) [@Eagel007](https://forum.inductiveautomation.com/u/Eagel007)\ **Post date:** [April 10, 2024, 11:23pm UTC](https://forum.inductiveautomation.com/t/issue-with-inline-frame-after-enabling-ssl/88666/5 "2024-04-10T23:23:54Z")
Another thing I just discovered is, the CSR file i got was from filling out ignition ssl wizard in gateway and we got SSL using that CSR. We cannot use same SSL for IIS since private key was not included. In that case we will need to redo the process to include IIS private key or build SSL using that private key and also import same private key to Ignition. Whats your thought ? ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [April 10, 2024, 11:25pm UTC](https://forum.inductiveautomation.com/t/issue-with-inline-frame-after-enabling-ssl/88666/6 "2024-04-10T23:25:17Z")
> [@Eagel007](#): > > We cannot use same SSL for IIS Why would you do that? ---
**Author:** ![Eagel007](https://avatars.discourse-cdn.com/v4/letter/e/7bcc69/32.png) [@Eagel007](https://forum.inductiveautomation.com/u/Eagel007)\ **Post date:** [April 11, 2024, 12:20am UTC](https://forum.inductiveautomation.com/t/issue-with-inline-frame-after-enabling-ssl/88666/7 "2024-04-11T00:20:08Z")
How else can it be done? ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [April 11, 2024, 1:54am UTC](https://forum.inductiveautomation.com/t/issue-with-inline-frame-after-enabling-ssl/88666/8 "2024-04-11T01:54:53Z")
It's a different server. It is supposed to have its own certificate. ---
**Author:** ![Eagel007](https://avatars.discourse-cdn.com/v4/letter/e/7bcc69/32.png) [@Eagel007](https://forum.inductiveautomation.com/u/Eagel007)\ **Post date:** [April 11, 2024, 2:12am UTC](https://forum.inductiveautomation.com/t/issue-with-inline-frame-after-enabling-ssl/88666/9 "2024-04-11T02:12:33Z")
Eventhough its on the same ip with different port than ignition? ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [April 11, 2024, 2:13am UTC](https://forum.inductiveautomation.com/t/issue-with-inline-frame-after-enabling-ssl/88666/10 "2024-04-11T02:13:32Z")
Yes, even though. All they might have in common is the same IP addresses and/or hostnames listed in the certificate. ---
**Author:** ![Eagel007](https://avatars.discourse-cdn.com/v4/letter/e/7bcc69/32.png) [@Eagel007](https://forum.inductiveautomation.com/u/Eagel007)\ **Post date:** [April 11, 2024, 2:02pm UTC](https://forum.inductiveautomation.com/t/issue-with-inline-frame-after-enabling-ssl/88666/11 "2024-04-11T14:02:12Z")
Also, we have a DNS name. Is the SSL cert supposed to be the same DNS name? ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [April 11, 2024, 2:03pm UTC](https://forum.inductiveautomation.com/t/issue-with-inline-frame-after-enabling-ssl/88666/12 "2024-04-11T14:03:07Z")
Yes.