Jump to content
Lukey103

ANSWERED Remote Access Freezing

Recommended Posts

Lukey103
Posted (edited)

Evening all,

 

I'm having trouble when I access my server remotely with an iphone. It starts fine and it after a short period of time it freezers for about 30 seconds before resuming. I have researched and tried to lower the quality but it still freezes when I am on the lowest 1080 setting.

 

Any help gladly received

 

thanks

 

 

 

Edited by Lukey103

Share this post


Link to post
Share on other sites
Lukey103
Posted (edited)

sorry fella I thought I'd included the log

 

 

Edited by Lukey103

Share this post


Link to post
Share on other sites
Luke

Can you please try lowering the in app quality setting and see if that helps? Thanks.

Share this post


Link to post
Share on other sites
Lukey103

Thanks Luke,

 

I have tried toggling the quality settings, it played fine on 1080 4MB for about 45 minutes then it started to periodically freeze, sometimes 30 secs or more before resuming. Also, as soon as I cut the video it allowed me to resume almost instantly before freezing again a few minutes later.

 

The same has happened for a couple of more 1080 videos I have tried, the issues always after a period of time of 30 mins or so

 

I tested a 1080 file at 720 1MB and it transcoded fine with plenty of buffer which was increasing by the minute, obviously want to steer clear from this because there was a noticeable picture quality difference and it's only a Pi after all.

 

For the record i have 20mb upload speed on my network and was using a 4g phone to test (appreciate that this isn't the best) however, it were someone remote playing on a steady 70mb download who alerted me of the freezes.

 

Do you 20mb is suffice for 1080 remote direct play?

Share this post


Link to post
Share on other sites
Luke

Yes, that is enough bandwidth, but there could be ISP throttling occurring at either side of the connection. Have you looked into that?

Share this post


Link to post
Share on other sites
Lukey103

Nice one Luke, I have tested it most of the night with a VPN connected on the client and it hasn't stopped once.

  • Like 1

Share this post


Link to post
Share on other sites
Luke

Thanks for the feedback.

Share this post


Link to post
Share on other sites
ramovilla

Hola, tengo un emby server instalado en un qnap y funcionando con un dominio personalizado y sin ningún problema con el certificado ssl, osea funciona el https. Aquí mis problemas, con el mismo dominio y certificado ssl lo instalo en una raspberry pi 4 y no consigo que me aparezca el puerto 8920 ni redirigiendo a otro puerto que se que está abierto por https://canyouseeme.org/  de hecho en la parte wam me aparece http://midomino.com:8096 tanto si cambio el puerto https como si no...

 

Hello, I have an emby server installed in a qnap and working with a custom domain and without any problem with the ssl certificate, I mean https works. Here my problems, with the same domain and ssl certificate I install it on a raspberry pi 4 and I cannot get port 8920 to appear nor redirecting to another port that is open by https://canyouseeme.org/ in fact in the wam part appears to me http:// mydomain.com:8096 both if I change the https port or not ...

Share this post


Link to post
Share on other sites
Luke
On 6/7/2020 at 3:20 PM, ramovilla said:

Hola, tengo un emby server instalado en un qnap y funcionando con un dominio personalizado y sin ningún problema con el certificado ssl, osea funciona el https. Aquí mis problemas, con el mismo dominio y certificado ssl lo instalo en una raspberry pi 4 y no consigo que me aparezca el puerto 8920 ni redirigiendo a otro puerto que se que está abierto por https://canyouseeme.org/  de hecho en la parte wam me aparece http://midomino.com:8096 tanto si cambio el puerto https como si no...

 

Hello, I have an emby server installed in a qnap and working with a custom domain and without any problem with the ssl certificate, I mean https works. Here my problems, with the same domain and ssl certificate I install it on a raspberry pi 4 and I cannot get port 8920 to appear nor redirecting to another port that is open by https://canyouseeme.org/ in fact in the wam part appears to me http:// mydomain.com:8096 both if I change the https port or not ...

Hi there, please attach the emby server log. thanks.

Share this post


Link to post
Share on other sites
ramovilla
Posted (edited)

Al parecer me da fallo el certificado, siendo el mismo que proporcioné en la versión de qnap que funcionaba ... De todas maneras voy ha hablar con mi ISP porque el tema de los puertos me sigue dando error.

Apparently the certificate fails me, being the same one that I provided in the qnap version that worked ... Anyway I will speak to my ISP because the issue of ports keeps giving me an error
 

embyserver (1).txt

Edited by ramovilla

Share this post


Link to post
Share on other sites
ramovilla

se me olvidó, permisos de root

I forgot, root permissions

Share this post


Link to post
Share on other sites
Luke

Are you all set now?

Share this post


Link to post
Share on other sites
ramovilla

Esperando al ISP y el servidor esta on, solo con http.
Es el mismo certificado que funciono en qnap ???

Waiting to my ISP... The Server on, with http only. Reading the log I saw the lane the certificate, it's the same certificate that world in qnap. ???

Share this post


Link to post
Share on other sites
Luke

You'd have to setup an ssl certificate in emby server network settings in order to use https.

Share this post


Link to post
Share on other sites
ramovilla

sigo sin entender la diferencia de certificado entre qnap y raspberry??, probaré con cerbot y let's encript...Teníais publicado un tutorial?!, me podrías refrescar la url, por favor.

I still don't understand the certificate difference between qnap and raspberry ??, I will try cerbot and let's encript ...Did you have a tutorial published?!, Could you refresh the url, please.

 

Share this post


Link to post
Share on other sites
Luke

Does this topic help?

 

Share this post


Link to post
Share on other sites
ramovilla

por su puesto; soy propietario de un dominio y mi entidad registradora me facilita un certificado ssl ( ionos ) y ese certificado sin instalar solo el fichero es el que me he llevado al nas qnap, y por otro lado en la herramienta network & virtual swicht sección DDNS he registrado el dominio que anteriormente registre en freedns.afraid.org y poder usar ip públicas.

of course; I am the owner of a domain and my registry entity provides me with an ssl certificate (ionos) and that certificate without installing only the file is the one that I have taken to the nas qnap, and on the other hand in the network & virtual swicht tool DDNS section I have registered the domain that you previously registered in freedns.afraid.org and be able to use public IPs.

Share this post


Link to post
Share on other sites
ramovilla

En synology es muy similar.. y tambien funciona muy bien.

En la Raspberry supongo que será cuestión del programa para encriptar-desencriptar

In synology it is very similar .. and it also works very well.

In the Raspberry I suppose that it will be a question of the program to encrypt-decrypt

Share this post


Link to post
Share on other sites
ramovilla

Encontrado el problema, la carpeta contenedora del certificado con cambiar el propietario como grupo a www-data y resuelto el problema (malditos, maravillosos permisos)

Found the problem, the folder containing the certificate with changing the owner as group to www-data and solved the problem (damn, wonderful permissions)

Share this post


Link to post
Share on other sites
Luke

Thanks for the feedback !

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...