aptalca

Community Developer
  • Content count

    1544
  • Joined

  • Last visited

Community Reputation

19 Good

About aptalca

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed
  1. Sorry, I forgot to respond to that. But there were a couple of issues. Url prefix should have been just the prefix, no forward slash. And the prefix option only applied to the calibre webserver, not the calibre gui. Calibre gui already has a prefix that can be used in reverse proxy situations. With the latest update the url prefix option has been deprecated. You can set that in the calibre gui webserver settings.
  2. Update pushed to calibre. Make sure you read the updated description on the docker hub page
  3. Symlink would have to point to the folder from the container's perspective. Easiest way to do that is, mount the volume /mnt as /mnt in container settings so the symlink is the same inside and out. Just point to the new location /mnt/user/share/etc
  4. Your network is super complicated. The fact that reverse proxy works from wan/4g but has issues from inside, suggests dns/firewall issues on the router. It may be nat loopback issues (many routers by default block connections that go out to the wan and come right back in to the router). You may also have issues with your firewall settings for connections between vlans. All those issues are really beyond the scope of our support for this image.
  5. "nginx -s reload" not working is not a bug. It's not supposed to work. That's not how nginx is launched in this image. Nginx is run and managed by the s6 supervisor. The way this image is set up is that, if there is no default config in the config folder, it copies the default one from inside the image, just like when you first install it. Also when someone messes up their settings, they can remove the default config file and restart the container to go back to the original setup. You're not supposed to remove the default config, but you can modify it to your heart's content. You can also add as many additional site configs as you like. Just don't delete the default one (you can leave it blank)
  6. Restart the container
  7. If you have plex set up to create index files, they take up a lot of space. They are all in a folder called "media" I believe and when I had a smaller cache drive, I had moved that to the array and put a symlink in its place
  8. Radarr does not auto update. Our docker images are refreshed every Friday so you'll get an update on unraid gui later today
  9. 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
  10. 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.
  11. 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
  12. 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.
  13. 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)
  14. 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
  15. 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.
Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.