buzzra

I just upgraded from 7.0.1 to 7.2.3. Smooth and no problems. Great job, thanks!

And that script will fix the 3rd party problem WITHOUT updating the docker? I want to continue to run the same old ass version that I am currently running that was working fine before the upgrade to 7.0.1.

I know this is old, but I still have a problem with this and really can't believe this was never acknowledged as a serious regression in the 7.0 upgrade. I have very old docker containers that now show as 3rd Party, as per the OP. I want to RUN these old containers as they are. I do not want to force an update or remove and re-add them. How do I get back all the management options THAT WERE REMOVED BY THE UNRAID UPGRADE PROCESS? Thanks for the help.

I WANT notifications disabled. My choice. Why does Unraid show this warning after I explicitly disabled notifications?!?!!? Please don't tell me why I need it on. Thanks for the help. buzz

Is this project still alive? Doesn't seem to be many recent updates. Are there any good alternatives?

What's the difference between RustDeskServer and RustDeskServer-Relay? I know there is an hbbs and hbbr parts to RustDesk, is that the difference here?So we need both of these dockers installed at the same time? -buzz

Also had the same problem. The above commands fixed it.

Nevermind. Deleted it. doesn't work and no support.

Hello, I just installed from Unraid Community Applications. No changes made to config. I go to http://myserver.mydomain.com:8438 and the Pinry homepage comes up. And that's it. I can't register, I can't login, and I don't know how to pin anything. Where do I go from here? I thought I read all the docs, but there is nothing about admin except editing the local_settings.py file, but no explanation of how to edit or why. Thanks buzz

That's wierd. I get connection failed in both Chrome and Firefox with HTTPS. Something strange about my setup I'll have to figure out. Thanks buzz

So, it only works via HTTP, but the link on the Unbalance settings page goes to HTTPS and you get an error. buzz

Funny you should ask. I was researching this too since my last post. My filesystem is ReiserFS, since I have had my Unraid up for quite a few years. I was thinking this may be the problem, because the only things I see about it online are problems with Windows NTFS and Mac HFS. I can move my cache drive to XFS, but that's not going to be any time soon. Does anyone else have this container running on a ReiserFS system? Any other suggestions are welcome. Thanks again for all your time on this. buzz

Still no good. cannot get to the webui. Still the same errors creating the database. init_db.log: Installing MariaDB/MySQL system tables in '/config/mysql' ... 2019-02-09 12:42:35 23429459561352 [ERROR] InnoDB: preallocating 12582912 bytes for file ./ibdata1 failed with error 95 2019-02-09 12:42:35 23429459561352 [ERROR] InnoDB: Could not set the file size of './ibdata1'. Probably out of disk space 2019-02-09 12:42:35 23429459561352 [ERROR] InnoDB: Database creation was aborted with error Generic error. You may need to delete the ibdata1 file before trying to start up again. 2019-02-09 12:42:36 23429459561352 [ERROR] Plugin 'InnoDB' init function returned error. 2019-02-09 12:42:36 23429459561352 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2019-02-09 12:42:36 23429459561352 [ERROR] Unknown/unsupported storage engine: InnoDB 2019-02-09 12:42:36 23429459561352 [ERROR] Aborting Installation of system tables failed! Examine the logs in /config/mysql for more information. The problem could be conflicting information in an external my.cnf files. You can ignore these by doing: shell> /usr/bin/mysql_install_db --defaults-file=~/.my.cnf You can also try to start the mysqld daemon with: shell> /usr/bin/mysqld --skip-grant-tables --general-log & and use the command line tool /usr/bin/mysql to connect to the mysql database and look at the grant tables: shell> /usr/bin/mysql -u root mysql mysql> show tables; Try 'mysqld --help' if you have problems with paths. Using --general-log gives you a log in /config/mysql that may be helpful. The latest information about mysql_install_db is available at https://mariadb.com/kb/en/installing-system-tables-mysql_install_db You can find the latest source at https://downloads.mariadb.org and the maria-discuss email list at https://launchpad.net/~maria-discuss Please check all of the above before submitting a bug report at http://mariadb.org/jira Sorry for the trouble. Thanks for the help buzz

I understand that, but you didn't answer the question. I would still like to see a change log of what was updated. Does such a thing exist, and if not, why? buzz

Is there anyway to see what changes are in each of these docker updates? I have done all of them, and the version number on the server management dashboard has not changed since v4.0.1.0. buzz

I followed the instructions above. Still not working. After removing the appdata folder and restarting the container, it comes up for a few seconds, creates the appdata folder and everything beneath it, and then stops. The init_db.log file is created with the same error. If I restart the container, it comes up and stays up, but I still can't get to the webui. I verified the changes to the 'run' file were still there. Here are the contents of current 'run' file and init_db.log: #!/usr/bin/with-contenv sh set -e # Exit immediately if a command exits with a non-zero status. set -u # Treat unset variables as an error. mkdir -p /run/mysqld chown $USER_ID:$GROUP_ID /run/mysqld echo "[$(basename "$(pwd)")] starting..." exec s6-applyuidgid -u $USER_ID -g $GROUP_ID -G ${SUP_GROUP_IDS:-$GROUP_ID} /usr/bin/mysqld --innodb-flush-method=fsync --datadir /config/mysql --tmpdir /tmp/ # vim:ft=sh:ts=4:sw=4:et:sts=4 Installing MariaDB/MySQL system tables in '/config/mysql' ... 2019-02-06 11:05:28 22602701859720 [ERROR] InnoDB: preallocating 12582912 bytes for file ./ibdata1 failed with error 95 2019-02-06 11:05:28 22602701859720 [ERROR] InnoDB: Could not set the file size of './ibdata1'. Probably out of disk space 2019-02-06 11:05:28 22602701859720 [ERROR] InnoDB: Database creation was aborted with error Generic error. You may need to delete the ibdata1 file before trying to start up again. 2019-02-06 11:05:28 22602701859720 [ERROR] Plugin 'InnoDB' init function returned error. 2019-02-06 11:05:28 22602701859720 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2019-02-06 11:05:28 22602701859720 [ERROR] Unknown/unsupported storage engine: InnoDB 2019-02-06 11:05:28 22602701859720 [ERROR] Aborting Installation of system tables failed! Examine the logs in /config/mysql for more information. The problem could be conflicting information in an external my.cnf files. You can ignore these by doing: shell> /usr/bin/mysql_install_db --defaults-file=~/.my.cnf You can also try to start the mysqld daemon with: shell> /usr/bin/mysqld --skip-grant-tables --general-log & and use the command line tool /usr/bin/mysql to connect to the mysql database and look at the grant tables: shell> /usr/bin/mysql -u root mysql mysql> show tables; Try 'mysqld --help' if you have problems with paths. Using --general-log gives you a log in /config/mysql that may be helpful. The latest information about mysql_install_db is available at https://mariadb.com/kb/en/installing-system-tables-mysql_install_db You can find the latest source at https://downloads.mariadb.org and the maria-discuss email list at https://launchpad.net/~maria-discuss Please check all of the above before submitting a bug report at http://mariadb.org/jira Thanks for your time and help! buzz

Yep, works when set to /tmp/NginxProxyManager. Will not work set to any user share on the array or the cache drive. Any ideas why? I have other Dockers running fine using the appdata share on the cache drive. I also have VMs running on another cache drive only share. Thanks for the help buzz

There are no errors in the Nginx logs, but this is the init_db.log: Installing MariaDB/MySQL system tables in '/config/mysql' ... 2019-02-01 2:06:01 22916083571592 [ERROR] InnoDB: preallocating 12582912 bytes for file ./ibdata1 failed with error 95 2019-02-01 2:06:01 22916083571592 [ERROR] InnoDB: Could not set the file size of './ibdata1'. Probably out of disk space 2019-02-01 2:06:01 22916083571592 [ERROR] InnoDB: Database creation was aborted with error Generic error. You may need to delete the ibdata1 file before trying to start up again. 2019-02-01 2:06:01 22916083571592 [ERROR] Plugin 'InnoDB' init function returned error. 2019-02-01 2:06:01 22916083571592 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2019-02-01 2:06:01 22916083571592 [ERROR] Unknown/unsupported storage engine: InnoDB 2019-02-01 2:06:01 22916083571592 [ERROR] Aborting Installation of system tables failed! Examine the logs in /config/mysql for more information. The problem could be conflicting information in an external my.cnf files. You can ignore these by doing: shell> /usr/bin/mysql_install_db --defaults-file=~/.my.cnf You can also try to start the mysqld daemon with: shell> /usr/bin/mysqld --skip-grant-tables --general-log & and use the command line tool /usr/bin/mysql to connect to the mysql database and look at the grant tables: shell> /usr/bin/mysql -u root mysql mysql> show tables; Try 'mysqld --help' if you have problems with paths. Using --general-log gives you a log in /config/mysql that may be helpful. The latest information about mysql_install_db is available at https://mariadb.com/kb/en/installing-system-tables-mysql_install_db You can find the latest source at https://downloads.mariadb.org and the maria-discuss email list at https://launchpad.net/~maria-discuss Please check all of the above before submitting a bug report at http://mariadb.org/jira It's definitely not a disk space problem as there is 369 GB available. edit: Sorry, after looking at my log file and going back through this topic, I see others have had this problem. My Settings -> Global Share Settings -> Tunable (enable DirectIO) is set to Auto. I have never changed it. My appdata share is normal as far as I know. I have a few other dockers running fine. It is on the cache drive, /mnt/user/appdata with 'use cache disk:' set to only.

I'm having a strange problem with this docker. I finally got the time to install it, and everything seemed to go fine. I left all the settings default, since there were no conflicts with other dockers or VMs my Unraid host. The problem is that I can't get to the webui. I try to connect to 'myunraidip:7818' and I get "This site can’t be reached x.x.x.x refused to connect." I can connect to :1880 and get the Nginx congratulations page. I did an Nmap scan of my host from another machine and I see all the ports I expect open, except 7818. Any ideas? buzz

Thanks for the explanation. Makes complete sense. And thanks Djoss for packaging this up in an Unraid container. I hope no one was offended by my questions. I just saw both and had not seen an explanation of the relationship. I will be installing this and moving my other containers to it. It looks to be VERY easy to manage. I have been using a sort of 'automatic' reverse proxy named nginx-proxy (https://hub.docker.com/r/jwilder/nginx-proxy/~/dockerfile/) but it took a lot to get it working in Unraid. Thanks again to everyone supporting this project. buzz

If I go to the homepage listed in the OP, https://nginxproxymanager.jc21.com, and then click on the githublink on that page, I get a different github repository than listed in the OP, https://github.com/jlesage/docker-nginx-proxy-manager. So which one is the correct one? It appears that the Unraid template is using the jlesage repository, but in a previous post here, someone requested feature requests and bugs be reported to the jc21 repository. So, what's the difference and which one should we be using? If I'm using jlesage version on Unraid, why report bugs to jc21? buzz

What's the trick to using the F-keys from webterminal? I can't seem to make anything work but the arrow and tab keys. Thanks buzz Edit: Never mind I figured it out. I was remoting from work to my home PC and launching webterminal. That won't work. F-keys get lost in the translation.

Can't believe this was taken away. I've never been on a forum that didn't let you search a specific topic. Any idea when this will be fixed? buzz

Thanks @aptalca that's just what I wanted to know. Any plans for fail2ban coming to this docker? Not a big deal, just wondering. Also, I read that the letsencrypt docker only does letsencrypt on one domain. If I wanted to use the LetsEncrypt service with multiple domains, Would it be best for me to try and modify this docker, or to start with the letsencrypt docker? Thanks again for the help and your work at LS! @dockerPolice, Sorry I didn't scroll down on the pop up to see that. Is there anyway for me to help in keeping these up to date, or does this need to be done by the maintainer? buzz

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