Jump to content
We're Hiring! Full Stack Developer ×

aptalca

Community Developer
  • Posts

    3,064
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by aptalca

  1. 50 minutes ago, matthope said:

    Hi,

     

    I have a small request, is it possible to make the config file /etc/php7/php-fpm.d/www.conf available in the appdata folder in unraid? I prefer to use php-fpm.sock instead of a port. Each time I update the docker, I need to go in the docker command line to change it, it's quite annoying.

     

    Regards, Mathieu

     

    Php updates tend to mess that up (they change the structure of those conf files). That's why we decided to internalize them to maintain control over them and update when necessary.

     

    I'm curious as the why you prefer sockets. In terms of performance, *theoretically* socket *may* provide better performance but according user testimonies, people don't notice a difference even on high traffic sites (> millions of hit per day). In any case it's just how nginx communicates with the php processor so it's all internal and there is no discernible effect for the end user or the admin. TCP port is the default in php so we went with that.

     

    If you really want to use your custom php config, you can always map a custom conf file as a volume, but keep in mind that it will likely break when php is updated and we won't provide you with further support ;-) you're on your own

     

    "-v /path/to/your/custom/www.conf:/etc/php7/php-fpm.d/www.conf" make sure you use the one in the container as the base

  2. I changed my mind and purchased an HDHomeRun Extend.  Installation with Plex seemed to go smoothly, but I couldn't figure out why I couldn't do any Live Streaming from my iOS device.  There wasn't a program guide for it or anything.  Then I noticed the version of Plex i had was something like 1.5 and I believe Plex needs to be 1.75 or above to accomplish Live Streaming.
     
    I suspect this is all happening because the initial docker I installed is not the one listed in this thread.  It probably is not being updated as often as the linuxserver.io version of Plex.  I've been using this other docker for Plex for ages, but it would be nice to have more recent updates for it.
     
    So I'm thinking about switching over to this one.  My question is, I guess there really isn't a smoother way of doing this...right?  My guess is I need to remove the Plex Docker I have now via the unRaid Dashboard, delete all the folders that might be left over on my cache drive for the Plex Server, and then install the linuxserver.io version from Community Apps basically from scratch.  Does this make the most sense?  


    Depending on what the other one is, you may be able to switch to the lsio one directly. Take a backup of your plex config folder if you don't want to lose it. Then remove the existing container and image. Don't remove the config folder. Install the lsio plex from community applications and set it to use the same config folder. Many people had success with that transition. In the container settings, set the version variable to latest and if you're logged into plex with a plexpass account, it will update to the latest plexpass version on start.

    Since you don't really mind starting over, worst case, you'll delete the plex config folder and start fresh. Nothing to lose.
    • Upvote 1
  3. Hdhr does not save anything anywhere. It rebroadcasts the ota tv signal over the network. That's all it does. Converts the ota signal to a signal/stream on your network that any device can access.

     

    Plex or whatever pvr client you use can access that network stream and do things with it like display it live or record it, etc.

     

    Hdhr connect's broadcast stream is mpeg2 (standard dvd format). Extend broadcasts in h264, which is a newer compression method that takes significantly less space and bandwidth.

     

    So the transcode I was referring to happens while extend is converting the ota tv signal to the network stream, before it reaches plex of other pvr client

     

     

    • Upvote 1
  4. As said before, hdhomerun is super easy to set up. Connect it to ethernet and then in plex go to add a dvr, it scans the network and finds the hdhomerun.

    With regards to hdhr connect and extend, the connect broadcasts the stream pretty much as is in mpeg2 format. Plex *can* transcode that if you set it to (marked experimental but works fine for me). Extend takes the mpeg2 stream and transcodes it to h264 before broadcasting over the network.

    If plex is running on a beefy server and you don't mind it transcoding, get the connect as it's cheaper. That's what I did.

    I haven't tried live TV because it's currently only supported on ios and android tv (not regular Android) clients and I don't have either of those.

    • Upvote 1
  5.  
    Any webui locks? 


    No, the webui is functional. Everything else works. It's just that one cpu core is pegged at 100% by the dd process and the preclear status no longer updated (temp files no longer update status, they are no longer written to)
  6. unRaid 6.3.5 and linuxserver.io's openvpn-as Docker container. Ive not read through this whole thread, so if the answer exists here already, please shove me in that direction.
    This was originally posted at Reddit, with no resolution so far.
     

    I followed Spaceinvader One’s 

     for setting up OpenVPN as a Docker container and was able to get everything set up correctly, save for one issue.

    Any time there’s an update to the container, the user I've created to access the VPN, not admin, is deleted. I can manually create the user via the command line, but should I have to?

    Why would updating/restarting the container cause the user to get removed? The user does show up in the UI, but I can’t connect using its credentials. When I do docker exec –it openvpn-as adduser username after restarting the container, I can connect again.

    What am I missing?



    Why are you adding users through command line? Do it through the gui. And change it to local first. It's in the docker image description
  7.  
     
    Anyone have any recommendations on what I could look at to try to solve this?


    I'm not sure what you're trying to accomplish, you have too many variables there that need to be validated, which makes troubleshooting very difficult.

    Plus, the listed config above is only listening on port 443 with ssl, but you're trying to connect to http, which is port 80 with no ssl.

    Why don't you start with the default config, see if you can access the welcome page so you can confirm the dns is correct? Then you can try the proxy.
  8. Thanks for all of the work here.  I've got nextcloud/letsencrypt working with duckdns, which I wouldn't have tried without the support here and tutorials.  One annoyance - is there an easy way to get unset urls (https://mydomain.duckdns.org/random_garbage) to map to 404 instead of the default "Welcome to our server?"
     
    Google searches for 404 and "welcome to our server" don't help...


    Google nginx 404 redirect
  9. The RDP-Calibre container I am using updated to the latest Calibre v3.0. Since then I cannot reach the server. I am not sure what is relevant in the logs. I did see this:
     
    calibre-server: error: no such option: --with-library
     
    Any suggestions where to start?


    Uh oh. Looks like they made some significant changes in 3.0

    I'll look into it
  10. Hi,
     
    I have a Feature Request: Would it be possible to add the support of multiple domains to the letsencrypt-docker in future?
     
    Br,
    Johannes


    We don't have plans for it. It makes the automation part super complicated and I haven't come up with a feasible way to implement it (without spending way too many dev hours)
  11. Just got notified that there was an update available, when I updated I'm no longer able to start the docker. Getting a "Execution error - Server error", but cant find anything in the logs.
     
    Anyone experiencing the same thing?


    I just updated mine and no issues here. You'll have to provide more info. Where did you see that error? Unraid gui? Docker log?
  12. Is this Nginx docker still being supported/updated? The LS hub.docker.com page shows it was last updated June 6th 2017, but the unRAID CA page shows it was last updated December 5, 2015. I already have wild card certs for my domains, so I do not need LetsEncrypt. I just need an Nginx proxy for my other dockers.
     
    Thanks for ALL the great work and support from the LinuxServer.io team!
     
    buzz


    Unraid template hasn't been updated with the changelog but the image is being updated. The docker hub page should have a more up to date changelog.

    Currently it is the same as the letsencrypt one except it is missing the cert parts and fail2ban
  13.  
    Still having the issue, [mention=7767]aptalca[/mention]? I could use your help to debug it.


    Hi@gfjardim

    I started another preclear through the plugin and it got stuck during post read. One cpu core is pegged at 100%. I'll leave it as is for now. Let me know what you need me to do to debug.
  14. Hi,
     
    Here is the Site-Conf:
     
    server {   listen 443 ssl;   server_name cloud.my-domain.at;   root /config/www;   index index.html index.htm index.php;   ###SSL Certificates   ssl_certificate /config/keys/letsencrypt/fullchain.pem;   ssl_certificate_key /config/keys/letsencrypt/privkey.pem;   ###Diffie▒..Hellman key exchange ###   ssl_dhparam /config/nginx/dhparams.pem;   ###SSL Ciphers   ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA';   ###Extra Settings###   ssl_prefer_server_ciphers on;   ssl_session_cache shared:SSL:10m;       ### Add HTTP Strict Transport Security ###   add_header Strict-Transport-Security "max-age=63072000; includeSubdomains";   add_header Front-End-Https on;   client_max_body_size 0;   location / {       proxy_pass https://192.168.1.252:443;       proxy_max_temp_file_size 2048m;       include /config/nginx/proxy.conf;   }}

    192.168.1.252 is the nextcloud docker. This docker is installed with "Host = none" and running on a dedicated IP (like LetsEncrypt as well).
     
    Ad 2) "letsencrypt will only work with one, but you can use both of them in nginx through creating separate server blocks in the site config"
    What does this mean? I can use reverseproxy with two domains but not SSL?
     



    I believe you need to modify the nextcloud site config to set the external domain.

    Letsencrypt in this docker image is set to work with one domain only. You can use two domains with this container as long as you do the cert retrieval and renewal manually for the second domain
  15. Hi,

     

    I have now installed LetsEncrpyt and Nextcloud on my UnRaid installation following the instruction here.

     

    I have 2 questions:

     

    1) When i connect to "cloud.domain.at" from my internal Subnet, then the URL is rewritten to "https://cloud.domain.at". If I do the same from public, then I am getting "https://_" in my url field and an error message "ERR_NAME_NOT_RESOLVED"..

     

    2) Can I use the same NextCloud and LetsEncrypt Docker installation with two different Domains? I have a private domain and I am also supporting an NGO with a seperate domain.

     

    Br,

    Johannes



    1) post your site config and we'll take a look. Likely you have a faulty url rewrite

    2) letsencrypt will only work with one, but you can use both of them in nginx through creating separate server blocks in the site config
  16. 1 hour ago, gfjardim said:

     

    Still having the issue, @aptalca? I could use your help to debug it.

     

    After seeing reports from others in other threads, I canceled that stalled preclear and started a new one using JoeL's script in a screen session. It is currently in post-read and has another 15 hours or so to go (8TB drives take forever). After that's done, I'd be happy to help debug.

    • Upvote 1
  17. I downloaded the current lsio version (1.7.2.3878) about 10 days ago.  DVR is working fine with HDHR Connect but I have no Live TV option.  Do I just delete this container and re-install to get that working or are there other things I need to do?
     
    Thanks!


    What client are you using? Live tv only works with Android tv and ios currently
  18. I am also having an issue with the plugin stalling. I am in the post-read step of a preclear of an 8TB disk, 22% in, it seems to have stalled. Percentage hasn't changed in hours, time elapsed is also stuck.

     

    htop shows the preclear script as running (pegging the cpu core at 100% constantly) and there are two other related active processes: "cmp - /dev/zero" and "dd if=/dev/sdb bs=2097152 skip=1 iflag=direct".

     

    Is the preclear still ongoing? Is it only the reporting aspect that is borked? Should I wait another 10 hours for it to finish?

     

    The preclear log only shows that the post-read has started, nothing after that.

     

    I checked the folder /temp/.preclear/sdb/ and the cmp_out, dd_output and the display_output haven't been modified in hours.

     

    Thanks

  19. Has anyone gotten the DVR part to work using a HDHR Connect? I can watch Live TV with the latest version but when I try to DVR something it plays fine for 15 seconds to a minute and then it's just all messed up. I figure since I can watch Live TV fine but can't DVR the same channel without it messing up that it's an issue somewhere with Plex or maybe how unraid is setup... I don't know. But I'd love to get DVR working!


    My hdhr connect is getting delivered today. I'll let you know within the next few days
  20. Is anyone able to get reverse proxying working for the Unifi docker?    I have this working for other dockers but not for Unifi.  
    From my LAN, before trying reverse proxying, hitting http://tower:8080 or https://tower:8443 will redirect to https://tower:8443/manage/account/login?redirect=%2Fmanage.
     
    When I try the following in my default file I will get a 404 error from Apache Tomcat.
        location ^~ /unifi {        include /config/nginx/proxy.conf;        proxy_pass http://192.168.1.99:8080;    }

    Same thing when I try

        location ^~ /unifi {        include /config/nginx/proxy.conf;        proxy_pass https://192.168.1.99:8443    }

    I also tried both of the above with trailing slashes after unifi.
     
    Any ideas on how to get this working?
     



    Base url to root reverse proxy often causes issues. Try the subdomain method.

    Or see if there is a way to have unifi use a base url as well
×
×
  • Create New...