Jump to content

allanp81

Members
  • Content Count

    284
  • Joined

  • Last visited

Community Reputation

7 Neutral

About allanp81

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I asked that before and was told there was no specific to use 1 over the other. I went for the docker route as I thought it was just easier to see how you're setting up directories for recordings etc. when using the docker interface. I think you still need the DVB plugin and then pass the device through to the docker. I use a networked HD Homerun so it just worked.
  2. Get the User Scripts plugin, that will allow you to set any schedule you like.
  3. I've got an N2 as well, great bit of kit and plays everything I've tried on it including near 100Gb UHD remuxes.
  4. Sorry I'm only running beta on my backup server currently which has no cache drives.
  5. It's so annoying, I had to re-architect my server to get around this problem (and obviously there was expense involved),.
  6. No I realise that, just wasn't sure if anyone was experiencing the same "issue". It seems to be a DNS issue, I'm getting different IPs returned when I look up my domain name depending on what computer I'm using.
  7. This seems to have stopped working for me this morning for no obvious reason. I've scanned all of the error logs and there's no errors logged that are any different to those that sporadically appear from time to time anyway. I'm perplexed.
  8. *EDIT* I think I answered my own question, seems to be a let's encrypt issue. My nextcloud instance seems to have stopped working this morning for no obvious reason. The nginx log is showing the following that it wasn't showing before: 2020/06/30 09:31:14 [error] 370#370: *355 directory index of "/config/www/" is forbidden, client: 192.168.7.28, server: _, request: "GET / HTTP/1.1", host: "192.168.7.11:8443" 2020/06/30 09:31:14 [error] 370#370: *355 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.7.28, server: _, request: "GET / HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.7.11:8443" 2020/06/30 09:31:14 [error] 370#370: *355 open() "/config/www/favicon.ico" failed (2: No such file or directory), client: 192.168.7.28, server: _, request: "GET /favicon.ico HTTP/1.1", host: "192.168.7.11:8443" 2020/06/30 09:31:14 [error] 370#370: *355 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.7.28, server: _, request: "GET /favicon.ico HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.7.11:8443" Anyone got any ideas as to why this has suddenly happened? The docker hasn't updated for a while I think but the let's encrypt docker last night did update.
  9. I've been using kodi with sql backend for years, using different versions of kodi for front end (coreelec, libreelec, kodi for windows, kodi headless docker) and never had any issues, just works.
  10. Just thought I'd chime in and say this worked for me on an old H67 board that refused to POST with any SAS cards in. I was able to get this to boot with 2 H310 SAS cards installed
  11. So the only change I've made recently is to install an NVME drive on the m.2 slot. As support for this was added later in a BIOS update I'm starting to suspect I have issues with this drive as I'm also suddenly seeing random AER PCI-E errors as well.
  12. Hi all, all of a sudden my server doesn't want to restart anymore. If I do a clean restart my server will post and then just sit on a black screen with a blinking cursor. BIOS is set to only boot this USB stick on legacy boot. I've just replaced the USB stick with a brand new one this morning and same issue. If I press the restart button on the server it will ALWAYS then successfully boot. My board is an Asrock X99 Extreme 4. downloadbox-diagnostics-20200403-1221.zip
  13. Just wondering why people seem to get these errors all of a sudden. The errors do say Corrected though.
  14. I've suddenly started getting these errors on my x99 chipset motherboard. Server is working fine as far as I can tell though. Mine is complaining about device [8086:6f02] which refers to "00:01.0 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 1 (rev 01)". Assuming that this refers to PCI-E slot 1 which had a graphics card I've tried moving it to a different slow but error is still appearing, albeit nowhere near as a frequently. I'm wondering if a docker update could somehow introduce this error as nothing has changed hardware wise.