• Content Count

  • Joined

  • Last visited

Community Reputation

9 Neutral

About jbreed

  • Rank

Recent Profile Visitors

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

  1. Deleted! Just now noticed this was an option and assumed this was the same module as I've always used. Thanks!
  2. Chezro, you can change the port mapping on either of the containers. For doing it here, modify host port 1 on the docker configuration page. This will map the port you set to the containers internal port 8843.
  3. This is due to using a self signed certificate, which is generally the same issue when accessing the UnRaid login page. To fix this you must create a local certificate authority, create a CSR, sign the certificate with the root CA, then upload it to the application. You would then need to install this root CA into your local machine you access these from, which if I recall Chrome uses the same CA store as we explorer although Firefox you have to import it into directly. Most of the time you can simply bypass this by choosing I understand or something of that nature to c
  4. I currently don't have an environment to test this and haven't used Nessus via a proxy before. Based on past posts here, it appears others have had it working. If there is something I can add to the Nessus container to make it easily configurable, then I'll happily add it. Just need some guidance on what is needed to get it working, or if I have the time I'll see about making a use case in my lab to test with it. I'll have to do some research on what changes are made to Nessus for doing this.
  5. Looking back into this and going over the documentation, there is a way to fix the login via going into the console. /opt/nessus/sbin/nessuscli chpasswd username If you don't remember the username, you can also add a new user with: /opt/nessus/sbin/nessuscli adduser
  6. For a temporary fix, I posted the commands to resolve this. I'll be pushing an update soon to resolve this without needing to console into the container and will also keep everything up to date without having to re-compile the image. Thanks!
  7. Update: The issue was I needing to include updating the container core components to avoid a mismatch from happening due to auto updates of plugins. To fix this before I push an update, you can do the following: Get a shell/console to the container. Type the following: /opt/nessus/sbin/nessuscli update --all service nessusd stop service nessusd start **confirmed you can also use the GUI to do this** Click the top-right button for your account, then go to my account. On the left-side menu, click 'about' Select the third tab fo
  8. Looking into this right now as I have the time to debug and re-package with the latest Nessus components. It may resolve simply by me updating the image and pushing an update. I'll know something by today. Thanks!
  9. Sorry for the late response, i've been pulled between multiple projects and need to revisit and update this. Upon initial setup, this does take some time as it has to pull all the latest plugins for scanning and such. I initially looked at if I could add all of these into the image so it shrunk the time and only added the new ones, but had some issues so I just left it as is (given it works, but takes some time on the first setup). After this initial setup it will be pretty quick to spin up compared to that first time. For login, (if I recall) you create the credentials
  10. Good question, I haven't attempted to set a bridge and I imagine it wouldn't have any issues. I'll have to test this myself to see what I can find out.
  11. hmm makes sense. What doesn't make sense is that it worked on 6.7.0 with 418.56 drivers and breaks when going to 6.7.1 or 6.7.2.
  12. Update pushed. If for some reason it doesn't show the update available, add this to your 'Template repositories:' section and 'check for updates' https://github.com/jbreed/docker-templates
  13. Thanks for the heads up, yes this is a bug. I should have it patched today.
  14. Had issues with upgrading before (breaks Plex with driver 430.14 on my GTX 760 ti). I decided to give it another shot, and finding the same issue. Doing some digging, inside the plexinc/pms-docker:plexpass PlexMediaServer console doing echo on $NVIDIA_VISIBLE_DEVICES shows correctly and correlates to the right GPU. Nvidia-smi also displays the following: -----------------------------------------------------------------------------+ | NVIDIA-SMI 430.14 Driver Version: 430.14 CUDA Version: 10.2 | |-------------------------------+----------------------+-----------