Trouble uploading video on course from linkedin

[Elias]

I currently have the problem loading linkedin videos, when playing the video it keeps loading and the following message appears>

The media could not be loaded, either because the server or network failed or because the format is not supported.

Perform a bypass but still, is there a solution for this?

[PhoneBoy]

Please provide some basic details about your environment (version, JHF level, blades enabled, especially if HTTPS Inspection is enabled).
Have you checked the logs when you try and upload videos to see if there are any errors?

[Elias]

I have https inspection enabled, I am using version R77.30.03, when I check the records it does not send me any errors, it appears that if you have access, the page can see without problems it is only a loading in a video of a Linkedin course.

[G_W_Albrecht]

Support for R77.30 has ended last september... If https inspection is disabled, but TP blades are still enabled, is the issue resolved then ?

[Elias]

Disable https inspection but it happens in the same way that the error still marks me:

The media could not be loaded, either because the server or network failed or because the format is not supported.

Note: 

Try pure internet connection, with the checkponint team outside the network, and the page works correctly when loading a video

[PhoneBoy]

If the gateway is actually blocking it, there should be specific drops shown in the logs.
You also have not mentioned (other than HTTPS Inspection) what Software Blades are enabled, which may be impacting this traffic.
What are the exact rule(s) that you are using that should be allowing this traffic?

[Elias]

Thank you for responding , this is what I see in the  logs as you can see if it allows  the step does not mark any error,  only at the  moment of starting the video marks the error mentioned .

We have several policies but we have a bypass fot https

[PhoneBoy]

I am less concerned about the HTTPS Inspection logs (especially since you put in a bypass rule) and more concerned what the other software blades had to say about the same connection.

[Elias]

i don´t understand very well what you mean by this: 

"more concerned what the other software blades had to say about the same connection."

[PhoneBoy]

Software Blades are "features" in the Check Point product.
You can see which ones are enabled in the relevant Gateway object in SmartDashboard.

Show me the other logs related to the connection from that host during the time this is happening.
Please also show the other rules in the Firewall and/or App Control policy that are allowing the connection.

You may need to have the TAC assist you in troubleshooting this.
That said, because you're on R77.30, which is no longer supported, if it turns out to be a bug, you may have to upgrade to resolve this issue.

[Elias]

These alarms appear in the gateway section 

[PhoneBoy]

The issue "Internal error occurred, could not connect to cws.checkpoint.com" is fixed in R80.10 and above, as shown here:
https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solut...
A reboot will likely clear this error temporarily.

In absence of other information from you, the only things I can suggest doing are opening a TAC case and/or upgrading to a supported release. Because you are using HTTPS Inspection, I highly recommend upgrading to R80.30.

[Elias · Accepted solution]

Good morning, thank you very much for the answers, fortunately we found the problem, the team was blocking a public ip from linkedin,