Jump to content

d8sychain

Members
  • Content Count

    38
  • Joined

  • Last visited

Community Reputation

1 Neutral

About d8sychain

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. Looks like I might need to brush the dust off of the project, make some changes and put out a MW v1.35. It comes with some nice changes to the MW core. Now that Parsoid has been ported to PHP, Node.js is no longer needed and can be dropped from this docker. Also MediaWiki 1.35 is the current stable long-term support release of MediaWiki and its end-of-life will be September 2023 https://www.mediawiki.org/wiki/Version_lifecycle In addition Alpine 3.12 was released May 2020
  2. @KDP The log looks normal. I don't see that it is trying to serve any pages. Example, after the last line in your log file should be followed with something like this: {"log":"- - 19/Oct/2020:03:40:00 +0000 \"GET /Main_Page\" 200\n","stream":"stderr","time":"2020-10-19T03:40:01.934684746Z"} {"log":"- - 19/Oct/2020:03:40:01 +0000 \"GET /load.php\" 200\n","stream":"stderr","time":"2020-10-19T03:40:02.644460091Z"} {"log":"- - 19/Oct/2020:03:40:01 +0000 \"GET /load.php\" 200\n","stream":"stderr","time":"2020-10-19T03:40:08.060153582Z"} {"log":"- - 19/Oct/2020:03:40:08 +0000 \"GET /load.php\" 200\n","stream":"stderr","time":"2020-10-19T03:40:08.771861407Z"} Might need to look at the NGINX log file also. Side note, if you are not to invested into this docker yet, you might want to try a different vision d8sychain/mediawiki:edge https://github.com/d8sychain/docker-mediawiki/tree/edge There are quite a few improvements to it vs d8sychain/mediawiki:latest. I never merged with 'latest' because basically I never finished updating the documentation that goes along with it.
  3. Get the Container ID number (you can this in the UnRaid UI docker tab, shown in advanced view) Use the following: cp "$(find /var/lib/docker/containers -name "Container ID*.log")" /mnt/user/appdata The log file will be located in the appdata folder
  4. The email issue sounds like an issue with the mediawiki code itself maybe. The issue with web access to mediawiki, I might be able to help, but I'm going to need some logs or some more info to go on.
  5. I'm really just guessing, but perhaps your issue is a combination with DNS, routing, and Cert matching. Have you tested connecting to the wiki internally (LAN) vs externally (WAN)? Can you provide some more details on your setup, PM me if you prefer.
  6. I did a quick search and from what I found SSL_ERROR_RX_RECORD_TOO_LONG is something that occurs exclusively on Firefox. This might help also -> https://cheapsslsecurity.com/blog/ssl_error_rx_record_too_long/ LetsEncrypt Wiki Config #wiki reverse proxy server { listen 443 ssl; root /config/www; index index.html index.htm index.php; server_name wiki.example.com; ssl_certificate /config/keys/letsencrypt/fullchain.pem; ssl_certificate_key /config/keys/letsencrypt/privkey.pem; ssl_dhparam /config/nginx/dhparams.pem; ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA'; ssl_prefer_server_ciphers on; client_max_body_size 0; location / { include /config/nginx/proxy.conf; proxy_pass http://UNRAID IP:PORT #; } }
  7. @Shirkie I'm sorry I haven't gotten back sooner. I'm in the middle of a large remodel/construction project in between my day job and everything else. I haven't touched development on this since February, so it's going to take me a min to get my head back into the code re-familiarize myself with it and I just don't have the time to do so right now. I have newer code / version, that has quite a few improvements and features than the "latest" build. Its version is "edge". I never merged the new code due to I hadn't finished updating all of the documentation that goes along with it. That being said, if you use the "edge" version it should eliminate any permission problems that your having. I've done quite a bit of testing and use "edge" version in 3 wiki projects of my own, and "edge" is solid with several built in tools/features to ease managing to mediawiki docker, it just lacks the updated documentation on how to use said features. Highlights: Bumping to Alpine v3.11 (lsiobase/nginx:3.11) Added OPTION to add MariaDB(MySQL) built into the container, providing a one-container-does-all, or you can run a separate MariaDB(MySQL) server (NEW FEATURE) MediaWiki Maintenance CLI Menu (NEW FEATURE) ExtensionManager (ENHANCED FEATURE) Backup functions (NEW FEATURE) Database functions (NEW FEATURE) Services functions (NEW FEATURE) MediaWiki file upload, logo, favicon settings changed see Change Log for details If you are not to invested in the current docker version for your wiki, I suggest starting with a fresh version of "edge" -> d8sychain/mediawiki:edge. It is possible to change over from "latest" to "edge", but there are some manual steps have to be taken, like deleting some files so that they get replaced with newer versions. They won't get replaced automatically just in case the end user has made any customization to the files to fit their specific needs , such as the NGINX config file.. If you have anymore problems or questions, don't hesitate to ask. I'll do what I can to answer them, just bare with my time constraints at this time.
  8. I'll try to get back with you tomorrow evening.
  9. Here was my steps: Remove the container and image click Add Container and select the hydra2 template change/update the Repository to linuxserver/nzbhydra2 click Apply Nothing else in the template needs to be changed, and no files or folders have be moved/copied, or renamed btw, I already had backup
  10. Sharing with the community in case someone hasn't seen this yet. https://nextcloud.com/blog/urgent-security-issue-in-nginx-php-fpm/
  11. @Bigsease30, I got MediaWiki working with the official MySQL image, although I had to jump through some hoops to get there. It requires a modification to the default configuration for MySQL 8.0.4 and above. See MySQL 8.0.4 : New Default Authentication. I'll outline what I did. Edit the MySQL template on UnRaid Create a new text file in `/mnt/user/appdata/mysql/conf.d` and name it something.cnf Edit the file and add the following: [mysqld] default_authentication_plugin = mysql_native_password Change the file permissions, if global has write permission MySQL will ignore the file Something like `chmod 644 something.cnf` Start the container and wait for it to run through the Entrypoint.sh script (took a few minutes) Check the container log and look for `[System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.18' socket: '/var/run/mysqld/mysqld.sock' port: 3306 MySQL Community Server - GPL.` Then it's ready If you have already started the container before creating the configuration file Stop the container Remove all of the database files in `/mnt/user/appdata/mysql/database` Restart the container Then you can use the MediaWiki installer to connect and complete the installation So, an alternative to all of that, use an older version of MySQL like 5.7 . MediaWiki currently supports MySQL 5.5.8+ Had no issues with MySQL 5.7
  12. @Bigsease30 Nevermind, I see that Bungy made several CA templates for several different images including the official MySQL image.
  13. I use linuxserver/mariadb for 3 wikis, and then use SQLite built into the MediaWiki docker for one that I run just for developing and testing. I also use linuxserver/mariadb for 2 NextCloud containers. So I have 5 linuxserver/mariadb containers running on one server, each one just set to a slightly different host port number. When I get a chance and I will try the MySQL docker that you where trying to use and see what happens. In your screenshot previously, it shows that you were trying to use the official mysql image. Could you clarify?
  14. My apologizes there. I have been working on changes to the docker all weekend and an updated/more informational README. Including instructions more specific to UnRaid, considering UnRaid is what I built this docker for. Also changes to the nginx.conf On MediaWiki installer set your Database host: 10.30.30.30:3306 (although if you are already using that port for a different MySQL container for NextCloud edit your MySQL database template that you are using for MediaWiki to say 3310 first then use the MediaWiki installer) Database username: root Database password: MY-PASS (based on the screenshots you provided). If you have any further problems let me know and I will try to help you through them as soon as I can. Also note, I just pushed new changes to docker tags `latest` and `1.33` (both are the same) late last night without realizing that going from 1.33-2 or older to 1.33-3 may cause problems for end users. If you haven't managed to get through the MediaWiki installer yet, then update the container 1st and delete /config/nginx/nginx.conf before proceeding then everything should be good. If you have completed the installer already and started using MediaWiki, delete the following files: /config/www/mediawiki/ExtraLocalSettings.php , /config/nginx/nginx.conf , Remove line 163 # Load extra settings and line 164 require ExtraLocalSettings.php'; from LocalSettings.php ,then restart the container. Any pages that you may have made in MediaWiki are all stored in the database and retained. Sorry for any inconvenience.
  15. The only part of the README that does not really apply to UnRaid is the docker run commands. Using CA and the UnRaid UI to add the container takes care of the docker commands. Point and click, browse to the URL for the container, use the Mediawiki installer to generate your LocalSettings.php file, download it to /mnt/user/appdata/mediawiki/www/mediawiki/ on your UnRaid machine (default) and you have a running wiki site.