when ingesting media via the live link hub using mono video, i am encountering an error in which the footage fails to ingest under jobs list. the error code as follows:
“LogCaptureManagerIngestJobExecutor: Error: [Ingest Executor 1] Ingest failed: Upload failed because the requested endpoint was not found: Portalis (Error code: 5)”
please help
Please select what you are reporting on:
Creative
What Type of Bug are you experiencing?
Other
Steps to Reproduce
1: open live link hub
2: change to capture manager
3: add device and hit mono video ingest
4:find directory where face recording is
5:click add to queue after selecting the footage
6:click on footage in job list and hit start.
Expected Result
processed footage of face ready to be mapped to meta human.
TL;DR Turn off your VPN and retry.
In most cases endpoint is started and available on an http port of a local PC (Portalis - in your case), default VPN settings may make the pc unavailable via network protocols/ports. You can actually see the status of the endpoint before starting ingest process (connected or not).
So, in general, it’s a network issue. Before clicking ‘start’, scroll the ‘Job details’ to the bottom and check if a host name is white/grey or yellow/orange. If it’s orange, then something is preventing Live Link Hub from connecting to http port of your destination pc (local PC, in most cases). You will see its status in right bottom corner and can check the logs - there is a message ‘Socket error detected when communicating with 192.168.1.X:YYYYY’.
After turning off a VPN, some time is needed for a network interfaces to return to usual settings (takes more than a minute sometimes in my case), then you’ll get a notification, that live link successfully connected (status will turn green). Only then you can click start the job. See the screens. Hope it will help.
Mine doesn’t connect and doesn’t even show ‘live link hub error’. It just doesn’t do anything.
The two apps, the editor and the hub, seem to be completely unaware of each other.
I just spent over an hour with Claude.AI and ChatGPT trying to solve this and both couldn’t.
I’m starting to think this is just a bug in 5.6 and we’ll just have to wait for it to be patched.
