Jump to content


Community Developer
  • Content Count

  • Joined

  • Last visited

Community Reputation

12 Good

1 Follower

About Bungy

  • Rank
    Advanced Member


  • Gender

Recent Profile Visitors

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

  1. Not that I know of. Containers generally run under the host's network stack. They don't work like virtual machines where each machine can have its own ip address.
  2. Set the network type back to the default. Then you should be able to connect to it using the host unraid system's ip address and port 3306
  3. Yep that's right. Glad you figured it out.
  4. Yeah, it works the same way. Just set VPN_ENABLED=<yes|no>
  5. Interesting. If people are finding my docker semi-useful, I'll have to devote some time into making it work better and more seamlessly. I'll pick this project back up and continue developing on it. Pull requests are always welcome!
  6. I'm planning on adding it to the container, but I have not yet. You're better off adding it to the container directly Sent from my SM-N950U using Tapatalk
  7. Try setting the environmental variable STRICT_PORT_FORWARD=no . That gets rid of the port forwarding, which was only really in place for binhex's arch-delugevpn docker container. I did that and doubled my speed. I'm currently using US-east. I haven't tweaked which one will give me the best results and just picked the one closest to me.
  8. I'm getting right at 10 MB/sec also. This *shouldn't* be using the port forwarding capabilities, but I'll double check to make sure it's not doing that setup.
  9. Set the environmental variables such as this: - GITLAB_EMAIL=gitlab@local.host - SMTP_HOST=smtp.gmail.com - SMTP_PORT=587 - SMTP_USER=youremail@gmail.com - SMTP_PASS=yourpassword - SMTP_STARTTLS=true - SMTP_AUTHENTICATION=login
  10. Yes, stop mysql docker. just rename your appdata folder for mysql and then restore the old data to the appdata folder If you don't have the root password, there's no way I know of to recover it. That would be a huge security flaw. When setting up the docker for the first time without any previous data, you set the environmental variable for MYSQL_ROOT_PASSWORD. If you still have that environmental variable set, it likely tells you the password you set up when you first started the docker. You can also set MYSQL_USER, MYSQL_PASSWORD, and MYSQL_DATABASE to set up those parameters as well.
  11. Yes, you can restore the appdata from 3 weeks ago and it'll revert your data back to that point. You'll just need to restore the mysql appdata. Without a user or root password, that's probably your only bet. If you have a user password, you should be able to backup the databases that user has access to. Yeah v8 has caused issues with some other apps I've used. In those cases, there was small fixes that I needed to do to get it to work, but restoring appdata will be the easiest way to get you back up and running.
  12. Also, can I ask what issue you're having with v8? It may be easiest to address those issues directly.
  13. Do you have backups of your appdata by any chance? Otherwise you may be forced to backup using mysql workbench under v8 and then restoring that data into v5
  14. Can you grab the logs from the docker container? something along the lines of this should work, you just may have to change "mysql" to your container name docker logs mysql