little bug on YouPHPTube-Encoder-Network

[maxlinux2000]

When the network server and an encoder reside on the same server, the network believes that the encoder is offline, even if it is working. I guess the ping is too low, and this is why the network declares the encoder offline. Have a look to the picture below at the ping values

[akhilleusuggo]

Well , that's not true . I have the encoder and network-encoder on the same server with 0.0018ms and still showing online

[DanielnetoDotCom]

@maxlinux2000 maybe there is something blocking the network to ping itself

[maxlinux2000]

I don `t believe it. I have added another server from another network (digitalocean in a germany vps) and it does the same. It is offline, even if it works perfectly. By the way the server "en3" runs on ubuntu 16.04 while the other two on ubuntu 18.04. I know it has nothing to do, but it's weird. Nor is it important ... it really works and ffmpeg does its job. It is just a curiosity.

But what does the network aggregator consider important to mark a server, such as "online"?

[DanielnetoDotCom]

Ido not have it on the top of my mind, but I am pretty sure is the serverStatus request

[maxlinux2000]

here the pictures of inpector (chrome this time) while en2 is encoding

[DanielnetoDotCom]

you have to look into the server status response of the offline encoder, if is possible open the request in a new tab (right click)

[maxlinux2000]

Hi, here the answer of server:

Access to XMLHttpRequest at 'https://en2.iesus.win/serverStatus' from origin 'https://network.iesus.win' has been blocked by CORS policy: The 'Access-Control-Allow-Origin' header contains multiple values ', ', but only one is allowed.

How to fix it?

[maxlinux2000]

OK Daniel

I think that we can fix this bug commenting one line in the Encoder-server at view/status.php. Just comment the header line

<?php
//header('Access-Control-Allow-Origin: *');
header('Content-Type: application/json');
require_once dirname(__FILE__) . '/../videos/configuration.php';

[DanielnetoDotCom]

Thanks for sharing this.

I am just afraid that will break something else.

some times I am in circles with the Cors and Access-Control-Allow-Origin issues.