Green Dragon

You get this going @Chazer?

Of course, YMMV! I'm certain that the UnRaid CA works great for the most recent, named release. However, if you wish to use the advanced functionality in the Beta versions then the standard CA template did not work for me (as of 3.0.0 RC7). This was primarily due to a few very important reasons: 1) Redis was required for use in the Betas 2) MariaDB was required for the Betas 3) If you wanted to run the betas alongside the release then you need to separate the systems 4) For whatever reason I could not get authentication in the Beta to work without putting the dockers on my lan with static addresses However you get it to work, GOOD LUCK and ENJOY!!!

Configure RomM 3.0.1.RC2 Dev Edition Docker Container in UnRaid To successfully install a RomM Dev (Beta) container on UnRaid I have developed this documentation to walk you thorough the process that works for me. You will have to install a MariaDB container which pretty much follow standard installation for the container. If you don't understand how MariaDB relates to RomM then try using my configuration settings below. You will have to build the RomM Dev container from scratch. If you are not comfortable with this then please reconsider running the Dev edition of RomM and just enjoy the out of the box container install found in the APP section of UnRaid. If you are experienced (or very brave) then please press on.... My specific configuration is shown. It works for me and so it should work for you. If you do not understand how container names and paths work you should try to follow the instructions to the letter. HOWEVER, your network is almost definitely different from mine so you MUST understand how UnRaid handles networks and you MUST understand static IP addresses and how to assign them in UnRaid dockers. My IP configurations listed below will almost certainly NOT work for your UnRaid installation! I can only get the RomM authorization system to work consistently with UnRaid using the custom (macvlan) 'br0--ETH01 (primary)' network that's been on my system since installed. I find that if you can set and ping a static IP address to each of the three containers then RomM Dev will work. Otherwise, the authentication system presents an 'Unable to login: CSRF token verification failed' message and I could never log in. I do not have enough of an understanding of this authentication system to say why it works or doesn't work. I only know that what's documented below works for me. YMMV! Please let me know if this works for you or if you are able to successfully login using any other UnRaid network type. NOTE: As of RomM 3.0.0 RC7, Redis is no longer required to be installed for RomM authentication to work. Questions? Contact me on UnRaid Forums or Discord; GreenDragon 1) INSTALL MARIADB: BROWSE TO: UnRaid/APPS/ SEARCH FOR: mariadb INSTALL FROM YOUR FAVORITE REPOSITORY (I use mariadb-official - mgutt's) INSTALL USING THE FOLLOWING PARAMETER OPTIONS: (NOTE: my config is shown, yours will probably differ where IP Address is concerned) NAME: MariaDB-RomMDev300 (this is what I use and it should work for you. must be unique to any other MariaDB installation in your system) NETWORK TYPE: 'Custom:br0--ETH01 (primary)' (yours will differ, see UnRaid documentation for network types) NOTE: You must use a custom LAN facing network and assign a static IP address that you can ping from your workstation IP ADDRESS: 172.16.1.156 (yours will differ, set for your network) NOTE: After install, you must be able to ping this address from your workstation Port: 3306 (default, no need to change unless you know it is used elsewhere on your network) Generate Random Password: yes (default, no need to change) Database Name: rommdev300 (this is what I use and it should work for you. should be unique to any other MariaDB/RomM installation in your system) Database User: rommdev300-user (this is what I use and it should work for you. should be unique to any other MariaDB/RomM installation in your system) Database Password: <set to whatever you choose but must match that configured in RomMDev300> Data: /mnt/user/appdata/mariadb-rommdev300/data (adjust for your path but the end of the path '/mariadb-rommdev300/data' should be used) NOTE: You will have to type this path in because it does not exist until the container is installed Config: /mnt/user/appdata/mariadb-rommdev300/config (adjust for your path but the end of the path '/mariadb-rommdev300/config' should be used) NOTE: You will have to type this path in because it does not exist until the container is installed CLICK 'APPLY ' 2) INSTALL ROMM DEV: BROWSE TO: UnRaid/DOCKER/ SCROLL TO BOTTOM CLICK 'ADD CONTAINER' ON THE FAR RIGHT, SWITCH TO 'ADVANCED VIEW' BY CLICKING 'BASIC VIEW' TOGGLE CONFIGURE AS FOLLOWS: NAME: RomMDev300 REPOSITORY: zurdi15/romm:3.0.0-rc.7 REGISTRY URL: https://hub.docker.com/r/zurdi15/romm ICON URL: https://github.com/Eurotimmy/unraid-templates/blob/main/RomM/RomM.png?raw=1 WEBUI: http://[IP]:[PORT:8080] NETWORK TYPE: 'Custom:br0--ETH01 (primary)' (yours will differ, see UnRaid documentation for network types) NOTE: You must use a custom LAN facing network and assign a static IP address that you can ping from your workstation IP ADDRESS: 172.16.1.155 (yours will differ, set for your network) NOTE: After install, you must be able to ping this address from your workstation NOTE: FOR THE REMAINING OPTIONS YOU WILL NEED TO ADD PORTS, PATHS, AND VARIABLES. TO DO SO FOR EACH, SCROLL TO THE BOTTOM CLICK '+ Add another Path, Port, Variable, Label or Device' USE THE DROPDOWN TO SELECT 'Port', Path', or 'Variable' FILL IN THE NECESSARY INFORMATION (SHOWN FOR EACH BELOW) ---PATH CONFIGURATION OPTIONS--- CONFIG TYPE: Port NAME: Container Port 8080 CONTAINER PORT: 8080 HOST PORT: 8092 (I use 8092 because my system already uses this port elsewhere. set yours accordingly) CLICK 'ADD' CONFIG TYPE: Path NAME: Config CONTAINER PATH: /romm/config HOST PATH: /mnt/user/appdata/rommdev300/ (adjust for your path but the end of the path '/rommdev300/' should be used) NOTE: You will have to type this path in because it does not exist until the container is installed CLICK 'ADD' CONFIG TYPE: Path NAME: Library CONTAINER PATH: /romm/library HOST PATH: /mnt/user/retrogaming/ (this is the path to YOUR roms folder. it can match your public RomM config. see RomM documentation for additional info) NOTE: You will have to type this path in because it does not exist until the container is installed CLICK 'ADD' CONFIG TYPE: Path NAME: Resources CONTAINER PATH: /romm/resources HOST PATH: /mnt/user/appdata/rommdev300/resources/ (adjust for your path but the end of the path '/rommdev300/resources/' should be used) NOTE: You will have to type this path in because it does not exist until the container is installed CLICK 'ADD' CONFIG TYPE: Path NAME: Assets CONTAINER PATH: /romm/assets HOST PATH: /mnt/user/appdata/rommdev300/assets/ (adjust for your path but the end of the path '/rommdev300/assets/' should be used) NOTE: You will have to type this path in because it does not exist until the container is installed CLICK 'ADD' CONFIG TYPE: Path NAME: Logs CONTAINER PATH: /romm/logs HOST PATH: /mnt/user/appdata/rommdev300/logs/ (adjust for your path but the end of the path '/rommdev300/logs/' should be used) NOTE: You will have to type this path in because it does not exist until the container is installed CLICK 'ADD' CONFIG TYPE: Path NAME: Redis-Data CONTAINER PATH: /redis-data HOST PATH: /mnt/user/appdata/rommdev300/redis-data/ (adjust for your path but the end of the path '/rommdev300/redis-data/' should be used) NOTE: You will have to type this path in because it does not exist until the container is installed CLICK 'ADD' ---IGDB SPECIFIC CONFIGURATION OPTIONS--- CONFIG TYPE: Variable NAME: IGDB_CLIENT_ID KEY: IGDB_CLIENT_ID VALUE: <this is specific to your configuration> (see RomM documentation for more info. if you are already running RomM Public Release you can copy/paste the value there) DESCRIPTION: Generate your 'Client ID' here: https://api-docs.igdb.com/#getting-started CLICK 'ADD' CONFIG TYPE: Variable NAME: IGDB_CLIENT_SECRET KEY: IGDB_CLIENT_SECRET VALUE: <this is specific to your configuration> (see RomM documentation for more info. if you are already running RomM Public Release you can copy/paste the value there) DESCRIPTION: Generate your 'Client Secret' here: https://api-docs.igdb.com/#getting-started CLICK 'ADD' ---MARIADB SPECIFIC CONFIGURATION OPTIONS--- CONFIG TYPE: Variable NAME: DB_HOST KEY: DB_HOST VALUE: 172.16.1.156 (yours will differ, but must match your MariaDB IP ADDRESS) CLICK 'ADD' CONFIG TYPE: Variable NAME: DB_NAME KEY: DB_NAME VALUE: rommdev300 (if you are following this documentation and using my configs this will work for you) CLICK 'ADD' CONFIG TYPE: Variable NAME: DB_USER KEY: DB_USER VALUE: rommdev300-user (if you are following this documentation and using my configs this will work for you) CLICK 'ADD' CONFIG TYPE: Variable NAME: DB_PASSWD KEY: DB_PASSWD VALUE: <this is specific to your configuration> (it must match 'Database Password' you set for MariaDB) CLICK 'ADD' CONFIG TYPE: Variable NAME: DB_PORT KEY: DB_PORT VALUE: 3306 (default, no need to change unless you know it is used elsewhere on your network) CLICK 'ADD' ---ROMM AUTHORIZATION SPECIFIC CONFIGURATION OPTIONS--- CONFIG TYPE: Variable NAME: ROMM_AUTH_USERNAME KEY: ROMM_AUTH_USERNAME VALUE: admin (default, no need to change until you have access to the system) CLICK 'ADD' CONFIG TYPE: Variable NAME: ROMM_AUTH_PASSWORD KEY: ROMM_AUTH_PASSWORD VALUE: admin (default, no need to change until you have access to the system) CLICK 'ADD' CONFIG TYPE: Variable NAME: ROMM_AUTH_SECRET_KEY KEY: ROMM_AUTH_SECRET_KEY VALUE: <this is specific to your configuration> DESCRIPTION: Generate a key with `openssl rand -hex 32` from an UnRaid global terminal CLICK 'ADD' ADDITIONAL NOTES AND LINKS: RomM website: https://romm.website/ RomM Repository: https://github.com/zurdi15/romm RomM Installation Documentation: https://github.com/zurdi15/romm/tree/release?tab=readme-ov-file#installation Upgrading RomM to 3.0: https://github.com/zurdi15/romm/wiki/Upgrading-to-3.0 Updated (3.0) config.yml: https://github.com/zurdi15/romm/blob/master/examples/config.example.yml

2.2.0 has just been released which fixes the STOP/START problem with having to reinstall the docker image. If you 'force update' you will receive the update ahead of distribution. It includes several fixes and nice enhancements.

Here are some thoughts: >>Have you been able to get this working consistently? Other than the problem with starting the container (as i described earlier) Im having very few problems. Having said that the platform is fairly new and so seems to have some performance issues and perhaps a little 'klunkiness'. (more on that later) >>The Twitch integration works fine, token fetched. Great! I've submitted a bug report on the support page for this. Another thing I've noticed (likely related) is that each time I use the STOP option UnRaid warns me that the container is 'already started' >>I get Romm working to the point where it's scanning the library and then it identifies my snes folder as the right console, but then finds nothing (already set up the folder structure exactly like the wiki says) or while searching the container just stops. This sounds as though your folders are incorrectly named (according to IGDB). They must match the folder from the website. Just go to IGDB, Select the 'Database' tab, then select 'Platforms' from the dropdown. This will bring up the list of supported gaming platforms on IGDB. Click the platform for which to get the folder name then check the last part of the URL to get the folder name. For EXAMPLE: If you need the name for the Amiga CD32 platform click 'Database', then 'Platforms', then the link for 'Amiga CD32'. You will be taken to the IGDB Amiga CD32 page. At the top of your browser find the URL which will end something like this '/platforms/amiga-cd32' (lead characters removed to stop linking). The name of the folder RomM is expecting to map it to the correct IGDB platform is that following the last / In this case the folder name will be 'amiga-cd32'. Note that if you do not want to change your folder names to match IGDB names you can use your existing folder names by mapping them in the config.yml file. In the section for 'platforms:' add a line indicating what your folder name is and what the IGDB folder name is. EXAMPLE amigacd32: 'amiga-cd32'. There are examples in the file. A word of caution on this; If you have both folders (yours and IDGB) EXAMPLE: both amigacd32 AND amiga-cd32 folders exist in your file system AND you have the mapping defined, RomM will create TWO entries for Amiga CD32 games in the left scrollbar index, both with the same titles. >>Once it stops once, it won't start again unless I edit the template like you are. I've deleted everything and tried again 3 times in the last week in case I was doing something wrong that I missed. This may be some of the 'klunkiness' I referred to earlier. Sometimes RomM 'appears' to be locked up, particularly when a scan is initiated. Because unless you select a specific platform to scan, RomM will always start from the top and scan each platform, comparing what it finds in the folder to what is in the database. I'm not sure if this would run faster with MariaDB instead of SQLite but that's something to consider. It will often appear to stop for a very long time (say, 3-5 minutes) when scanning an already populated platform, no doubt driven by the number of titles in that platform. I have found that opening and monitoring the 'logs' option in UnRaid Docker interface (left-click the RomM Docker icon then select 'logs') you can follow what RomM is doing. You will see some interesting entries there. Its really only useful for monitoring scans though as web activity logging is quite 'busy'. Its a new platform and the authors are working through bugs and feature requests. This is a GREAT system but as with all new systems, it can be improved. Having said that I am so happy with it I supported the author with a donation, will continue to do so as long as it is maintained, and will encourage others to do so as well. >>Once it stops once, it won't start again unless I edit the template like you are. I'm guessing its not actually 'stopped' but busy (see above) but I could be wrong. I've learned to be patient. If I think I have a problem I'll wait at least FIVE minutes before 'reloading' the container and starting again. >>I've also tried using the experimental redis options, setting up auth, just to see if I get a different outcome but it's always the same. I have changed nothing aside from folder names and mappings in the config.yml (as described above) and RomM seems to work fine with my EXTENSIVE list of platforms and titles. >>I've deleted everything and tried again 3 times in the last week in case I was doing something wrong that I missed. I'm very sorry that you're experiencing issues. Hopefully, you will find something helpful in this response. Let me know if I can help in any way!

These errors basically indicate that it could not find the title in IGDB. if you look at the lines above and below these 'errors' you will see the title it could not find.

I found that (in unraid) I have to 'edit' the docker template each time I stop the container. Simply toggling the network type back and forth (thus enabling the 'apply' button) then clicking 'apply' gets the container running. Each time it 'successfully retrieves a token'.

I gotta say; This app is AMAZING! I've waited for a very long time for something like it! I'm spending the holidays importing ROMS and despite the few minor problems I've found thus far, I'm very happy with the project and confident that it will only get better over time!!! Time to go support the author!!! THANK YOU!

Scan engine opportunities: 1) After a period of time the scan engine stops displaying progress (found/not found) in the browser. Log shows its still running and finding/not finding titles. 2) Before I learned to check the logs (for op 1) I restarted a few scans. After doing so I found that there were many duplicates. Devs may want to put some duplicate checking into the scan engine?

Do the environment variables work if added to the config.yml? Or only if in docker template? If not, would be nice if they did. ENABLE_SCHEDULED_RESCAN: Whether to rescan on a schedule SCHEDULED_RESCAN_CRON: Cron expression for scheduled rescan ENABLE_SCHEDULED_UPDATE_SWITCH_TITLEDB: Whether to update the switch title database on a schedule SCHEDULED_UPDATE_SWITCH_TITLEDB_CRON: Cron expression for scheduled switch title database update ENABLE_SCHEDULED_UPDATE_MAME_XML: Whether to update the MAME XML on a schedule SCHEDULED_UPDATE_MAME_XML_CRON: Cron expression for scheduled MAME XML update

HAHAHAHA! three words WORKED! OOF! Thanks!

Nope! No joy... (thanks for the suggestion tho)

I am unable to register an application on twitch. Entered all data, clicked 'Create' and ...nothing Tried multiple browsers. Tried incognito. Still, no joy... Thoughts? Suggestions?

I have the latest version of CA Mover Tuning installed (2023.08.22) and still I see this error on boot. No other problems, just an entry on the boot screen. Must I simply remove and reinstall to remove the error? Thanks!

Thanks for the suggestion! That thread seems to suggest that I add 'pcie_aspm=off' to the boot options. However, I already have several options set there over the years. Im not very good with the config syntax. Can you help me determine the proper placement of the suggested 'pcie_aspm=off'? Here is what my config section looks like today: label Unraid OS menu default kernel /bzimage append initrd=/bzroot pci=noaer append initrd=/bzroot nvme_core.default_ps_max_latency_us=0 label Unraid OS GUI Mode Thanks!!

Ive been receiving alot of these syslog errors since installing a JMB585 NVMe M.2 5 Sata Adapter. Ive done some searching but unable to find this specific error so will need assistance from someone far more experienced than I. I am including a system diagnostics export. Thanks for looking. gothamcity-diagnostics-20231123-1140.zip

So, you still run VM Backup?

All back to normal now. Thanks! BTW: I was told that the author of this plugin is no longer supporting it. Is this true? What alternative is out there? Thanks again!

I restored the VM from the previous day using the script. Looked to go well but failed to start with "internal error: Failed to reserve port 5700". Checking the restore xml it looks to be the display port. Im not sure how to troubleshoot or work around that error.

This morning I found that one of my VMs will not start following a backup failure. Im using the 'VM Backup' plugin by JTok. Previous days backups look complete but this mornings backup (.zst) of that vm is not there (only the .xml exists). I did not take a screenshot of the backup failure error and cannot now access the vm backup log. I get an 'undefined' error when trying. Probably because libvert will not start. Restarting VM Manager results in a Libvert error: "2023-10-31 13:44:08.174+0000: 24168: error : virQEMUFileOpenAs:11390 : Failed to open file '/mnt/user/domains/W2K3_the_rock_bbs/vdisk1.snap': No such file or directory" Libvert can only be started via a complete shutdown and restart of UnRaid. '/mnt/user/domains/W2K3_the_rock_bbs/vdisk1.img' exists '/mnt/user/domains/W2K3_the_rock_bbs/vdisk1.snap' does not. Is this a backup tmp file? Not only do i need to fix, id like to understand what went wrong. This system has been working flawlessly for a very log time and I don't see any other failures in the system.

Thanks I shall do that.

This morning I found that one of my VMs will not start following a backup failure. Im using the 'VM Backup' plugin by JTok. Previous days backups look complete but this mornings backup (.zst) of that vm is not there (only the .xml exists). I did not take a screenshot of the backup failure error and cannot now access the vm backup log. I get an 'undefined' error when trying. Probably because libvert will not start. Restarting VM Manager results in a Libvert error: "2023-10-31 13:44:08.174+0000: 24168: error : virQEMUFileOpenAs:11390 : Failed to open file '/mnt/user/domains/W2K3_the_rock_bbs/vdisk1.snap': No such file or directory" Libvert can only be started via a complete shutdown and restart of UnRaid. '/mnt/user/domains/W2K3_the_rock_bbs/vdisk1.img' exists '/mnt/user/domains/W2K3_the_rock_bbs/vdisk1.snap' does not. Is this a backup tmp file? Not only do i need to fix, id like to understand what went wrong. This system has been working flawlessly for a very log time and I don't see any other failures in the system.

Question: Why this line: 2023-10-11 10:33:41.655184 [info] VPN remote server(s) defined as 'ip,' Mine contains addresses for my DNS servers (perhaps youre just being cautious and edited for security)?

After upgrading to 6.12.4 my docker containers cannot communicate between networks. I have been running radarr and sonarr on a custom (macvlan) and qbittorrent docker on the default bridge networks for years with no network related problems. Shortly after upgrading to 6.12.4 I found that the dockers on different networks can no longer communicate. I tested pinging across all dockers (I have many others) and indeed nothing on the custom 'br0' network can ping anything on the default bridge network and vice-versa. I checked the relevant docker network configs and do not find anything to indicate why this would now be a problem. Of course, I have restarted everything (dockers, unraid, switch, router) and still no joy. Any sage advice would be very much appreciated! (diags attached) gothamcity-diagnostics-20230928-2206.zip

Well now today I am able to login to the webui and seeding is working fine but none of the other dockers pointing to this one (sonarr, radarr, etc) are able to connect. As indicated before, QBitTorrentVPN is on the default (ip) bridge network while the other dockers are on a custom (macvlan) network. All work fine otherwise. Essentially, nothing is able to connect to QBitTorrentVPN since the last UnRaid and QBitTorrentVPN updates. One of those updates 'fixed' something which has sporatically 'broken' QBitTorrentVPN. Ill work more on this after work tonight... <sigh>