Siwat2545 Posted July 4, 2020 Author Share Posted July 4, 2020 17 hours ago, muwahhid said: will it end? Can I see your log and your config? Quote Link to comment
muwahhid Posted July 4, 2020 Share Posted July 4, 2020 (edited) 7 hours ago, Siwat2545 said: Can I see your log and your config? this error has already been voiced here. But I didn’t find an answer Edited July 4, 2020 by muwahhid Quote Link to comment
FantasyNoobs Posted July 11, 2020 Share Posted July 11, 2020 (edited) Hello everyone, I need your help. I have set up my nextcloud container with a letsencrypt container (reverse proxy) and a OnlyOfficeDocumentServer container. My nextcloud is accessible from wan and lan, because in my pfsense (main router/firewall) i've set NAT to point to letsencrypt (and check the NAT reflection). So i'm there : When i enter nextcloud.mydomain.com i can access nextcloud UI. When i enter office.mydomain.com i can access the "Thank you for choosing ONLYOFFICE! - Document Server is running" page of OnlyOffice. But when i install the OnlyOffice app for NextCloud, and i try to set the DocumentServer Adress (https://office.mydomain.com/), i get this error : -> Error while trying to connect (cURL error 28: Failed to connect to office.xxxxx.xxxxx port 443: Operation timed out (see https://curl.haxx.se/libcurl/c/libcurl-errors.html)) In my PFSense box, i tried to look at the log to find a blocked packet, but i'm lost. Can you guys help me please ? Thanks a lot ! Edited July 11, 2020 by jonathanm removed actual valid url from error Quote Link to comment
Siwat2545 Posted July 13, 2020 Author Share Posted July 13, 2020 On 7/11/2020 at 9:30 PM, FantasyNoobs said: Hello everyone, I need your help. I have set up my nextcloud container with a letsencrypt container (reverse proxy) and a OnlyOfficeDocumentServer container. My nextcloud is accessible from wan and lan, because in my pfsense (main router/firewall) i've set NAT to point to letsencrypt (and check the NAT reflection). So i'm there : When i enter nextcloud.mydomain.com i can access nextcloud UI. When i enter office.mydomain.com i can access the "Thank you for choosing ONLYOFFICE! - Document Server is running" page of OnlyOffice. But when i install the OnlyOffice app for NextCloud, and i try to set the DocumentServer Adress (https://office.mydomain.com/), i get this error : -> Error while trying to connect (cURL error 28: Failed to connect to office.xxxxx.xxxxx port 443: Operation timed out (see https://curl.haxx.se/libcurl/c/libcurl-errors.html)) In my PFSense box, i tried to look at the log to find a blocked packet, but i'm lost. Can you guys help me please ? Thanks a lot ! can you ping the address from nextcloud docker? Quote Link to comment
FantasyNoobs Posted July 13, 2020 Share Posted July 13, 2020 (edited) 8 hours ago, Siwat2545 said: can you ping the address from nextcloud docker? Hello Siwat2545 and thank you for your time. I can't ping office.mydomain.com from nextcloud container. But i can with my computer. I can ping the app IP (172.19.x.x) with nextcloud container. I think that it may be a problem with my pfsense box, because when i try to ping office.mydomain.com with nextcloud container, it receive the right adress (my public IP) but doesn't get any response. Only office, nextcloud and letsencrypt are all three on the same docker network created for them. Thanks ! EDIT : I fixed my problem with wireshark and long investigate. I've seen that when nextcloud try to communicate with OnlyOffice through https://office.mydomain.com, when the packet arrive at my pfsense router/firewall box, it is like this : FROM 10.10.X.X (IP Unraid) TO 127.0.0.1:19001 And i'm a 'block all' type of guy, so i've set pfsense to allow pack from unraid to web only on HTTP and HTTPS port. So i added a rule to let Unraid IP send packet to 127.0.0.1:19001 But i'm a little confuse about that. It works, and i see packets from unraid to 127.0.0.1:19001 pass through when i test OnlyOffice from Nextcloud, but if i'm not to bad, 127.0.0.1 is localhost, so it doesn't have to go to the pfsense box... But the problem is fixed so it's ok If someone can understand this, its a big plus ^^ Hope that will fixes some people's problems (Sorry for my poor English) Edited July 13, 2020 by FantasyNoobs Problem solved Quote Link to comment
Darren Cook Posted July 17, 2020 Share Posted July 17, 2020 In H256size does this support nvidia card passthrough? as no mention of it that ive seen? Quote Link to comment
Siwat2545 Posted July 21, 2020 Author Share Posted July 21, 2020 On 7/13/2020 at 9:58 PM, FantasyNoobs said: Hello Siwat2545 and thank you for your time. I can't ping office.mydomain.com from nextcloud container. But i can with my computer. I can ping the app IP (172.19.x.x) with nextcloud container. I think that it may be a problem with my pfsense box, because when i try to ping office.mydomain.com with nextcloud container, it receive the right adress (my public IP) but doesn't get any response. Only office, nextcloud and letsencrypt are all three on the same docker network created for them. Thanks ! EDIT : I fixed my problem with wireshark and long investigate. I've seen that when nextcloud try to communicate with OnlyOffice through https://office.mydomain.com, when the packet arrive at my pfsense router/firewall box, it is like this : FROM 10.10.X.X (IP Unraid) TO 127.0.0.1:19001 And i'm a 'block all' type of guy, so i've set pfsense to allow pack from unraid to web only on HTTP and HTTPS port. So i added a rule to let Unraid IP send packet to 127.0.0.1:19001 But i'm a little confuse about that. It works, and i see packets from unraid to 127.0.0.1:19001 pass through when i test OnlyOffice from Nextcloud, but if i'm not to bad, 127.0.0.1 is localhost, so it doesn't have to go to the pfsense box... But the problem is fixed so it's ok If someone can understand this, its a big plus ^^ Hope that will fixes some people's problems (Sorry for my poor English) What's your NAT reflection Setting? Quote Link to comment
Siwat2545 Posted July 21, 2020 Author Share Posted July 21, 2020 On 7/18/2020 at 1:27 AM, Darren Cook said: In H256size does this support nvidia card passthrough? as no mention of it that ive seen? It does not, currently. Quote Link to comment
FantasyNoobs Posted July 21, 2020 Share Posted July 21, 2020 11 minutes ago, Siwat2545 said: What's your NAT reflection Setting? I have just set the “Nat reflection + proxy” setting on each bat rule of my reverse proxy in offense. just to be able to access my Nextcloud with nextcloud.mydomain.com when I’m in the lan network. Quote Link to comment
Siwat2545 Posted July 21, 2020 Author Share Posted July 21, 2020 12 minutes ago, FantasyNoobs said: I have just set the “Nat reflection + proxy” setting on each bat rule of my reverse proxy in offense. just to be able to access my Nextcloud with nextcloud.mydomain.com when I’m in the lan network. 12 minutes ago, FantasyNoobs said: I have just set the “Nat reflection + proxy” setting on each bat rule of my reverse proxy in offense. just to be able to access my Nextcloud with nextcloud.mydomain.com when I’m in the lan network. I used that too, mine works though Quote Link to comment
FantasyNoobs Posted July 21, 2020 Share Posted July 21, 2020 4 minutes ago, Siwat2545 said: I used that too, mine works though Without the need to create a 127.0.0.1:19001 rule ? Quote Link to comment
Siwat2545 Posted July 21, 2020 Author Share Posted July 21, 2020 1 minute ago, FantasyNoobs said: Without the need to create a 127.0.0.1:19001 rule ? Yea, i used HAProxy through not just port forward Quote Link to comment
FantasyNoobs Posted July 21, 2020 Share Posted July 21, 2020 Just now, Siwat2545 said: Yea, i used HAProxy through not just port forward Ah ok. but it work so it’s not really a problem. maybe I see 127.0.0.1 on pfsense because the NAT reflection translate my domain to local host to return to the same network. thanks for all Quote Link to comment
gacpac Posted July 22, 2020 Share Posted July 22, 2020 I'm using h265ize. Is this a software encoder or is it able to use intel quicksync or nvidia nvenc? With an i5 encoding a 30 minute video takes around 35 minutes, running at 0.70x Quote Link to comment
Siwat2545 Posted July 22, 2020 Author Share Posted July 22, 2020 2 hours ago, gacpac said: I'm using h265ize. Is this a software encoder or is it able to use intel quicksync or nvidia nvenc? With an i5 encoding a 30 minute video takes around 35 minutes, running at 0.70x Using NVENC will require me to recompile ffmpeg with NVIDIA encoder support, which I am currently doing right now. Quote Link to comment
gacpac Posted July 22, 2020 Share Posted July 22, 2020 Using NVENC will require me to recompile ffmpeg with NVIDIA encoder support, which I am currently doing right now.Ooooh niceee. And what about quicksync?Sent from my Pixel 2 XL using Tapatalk Quote Link to comment
Siwat2545 Posted July 22, 2020 Author Share Posted July 22, 2020 1 hour ago, gacpac said: Ooooh niceee. And what about quicksync? Sent from my Pixel 2 XL using Tapatalk I might add quick sync in the future, but currently all my server are running on Xeon platform without iGPU so I cannot test the image. Quote Link to comment
gacpac Posted July 22, 2020 Share Posted July 22, 2020 I might add quick sync in the future, but currently all my server are running on Xeon platform without iGPU so I cannot test the image.I wouldn't mind testing lol. My encoding is taking forever and I love this plugin. Sent from my Pixel 2 XL using Tapatalk 1 Quote Link to comment
Siwat2545 Posted July 22, 2020 Author Share Posted July 22, 2020 3 hours ago, gacpac said: I wouldn't mind testing lol. My encoding is taking forever and I love this plugin. Sent from my Pixel 2 XL using Tapatalk if you're free, pm me on discord, SiwatS#2244 I'll send you the testing instructions Quote Link to comment
gacpac Posted July 25, 2020 Share Posted July 25, 2020 Hello, Is it normal that h265ize is croppin the video from 1920x1080 to 1920x1072? Quote Link to comment
ryan.m Posted July 29, 2020 Share Posted July 29, 2020 On 7/26/2020 at 7:07 AM, gacpac said: Hello, Is it normal that h265ize is croppin the video from 1920x1080 to 1920x1072? You'll need to add an option to the H265ize command "--normalize-level 0". This will prevent it from auto-cropping the video. I don't know how to pass that command through to the docker container, actually what I come here to ask, anyone got any tips? Quote Link to comment
Siwat2545 Posted July 29, 2020 Author Share Posted July 29, 2020 25 minutes ago, ryan.m said: You'll need to add an option to the H265ize command "--normalize-level 0". This will prevent it from auto-cropping the video. I don't know how to pass that command through to the docker container, actually what I come here to ask, anyone got any tips? I'll add that as an option in the next release Quote Link to comment
ryan.m Posted July 30, 2020 Share Posted July 30, 2020 Thanks for your work on putting the container together Swiat. Is there a way to pass through our own commands to h265ize when we build the docker container? This seems like it would be better than troubling you for a new feature if we wanted to tweak the encode settings. I've tried adding variables to the container, but I'm not all that strong with docker and was mostly guessing and couldn't get it to work. Quote Link to comment
Wong Posted August 10, 2020 Share Posted August 10, 2020 Is it possible to setup OnlyOffice without using Reverse Proxy? Currently, I am getting Bad Health Check Status. I have setup up a CNAME onlyoffice.protech.my My domain name is protech.my. I have left a screenshot below that I am having trouble with. Quote Link to comment
gacpac Posted August 15, 2020 Share Posted August 15, 2020 I'll add that as an option in the next releaseYou are awesome dude. That's all I want to say, I've been meaning to test the beta you have, ran into couple issues on my side. I'll text you later if you are available. Sent from my Pixel 2 XL using Tapatalk Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.