UNOPARATOR

Thanks for this and every other plugin you bring to our table. Can you suggest a usage video if you know any? ;)

F12 or the keyboard shortcut might be something else if you are using macOS or something else, just look for "Developer Tools" in the menus. @BZwart

He may get a lot of PMs which he can't keep up with, maybe @Squid would help as a different tactic.

It is waiting for approval on the CA's side in order to be listed.

Still no news about plugin availability on CA?

The first post's content from the old plugin has some links missing, ie. links under CUSTOM CSS/SCRIPT. Thanks for picking up the plugin and making us all happy.

The problem lies within the docker image of the latest Apache NiFi 2.x versions, even though you set the NIFI_WEB_HTTP_PORT port and not the NIFI_WEB_HTTPS_PORT, NIFI_WEB_HTTPS_PORT gets assigned which results an error indicating you cannot use both HTTP and HTTPS at the same time. And even when you try to just use HTTPS the "Invalid SNI" error occurs since v2.x HTTPS without a valid SSL certificate gives this error. I tried to use Swag to create a certificate and use that but I couldn't succeed.

It seems that Fix Common Problems plugin is reporting that CA doesn't know the addon which USB_Manager installs:

Or maybe try another .jar such as https://papermc.io/, I have been running mine with paper since v1.16. With several Spigot plugins + GeyserMC for crossplay between Java & Bedrock/mobile versions.

Try increasing JAVA_INITIAL_HEAP_SIZE and JAVA_MAX_HEAP_SIZE values in the template.

It was previously possible to scroll, when you start/restart the container and immediately open up the web ui or if the tab was not sleeping. After a refresh of the web ui, it generally was showing just a single page full of logs or less. It's been awhile since I checked out the MCServer, just noticed this behaviour after updating papermc and installed plugins then opened up web ui to see any plugin errors were being logged. But due to the nature of start up as many lines of logs are written one after another, not being able to scroll at all, really limits the usefulness of the web ui (at least for me). I'm not a MC or Java expert but if you would provide some details about the current approach, I might come up with an idea being in software development nevertheless.

I was just wondering about the same issue.

I was able to get the WebUI working after manually creating a variable named "NIFI_WEB_HTTP_PORT" and setting it the same as "Web Interface HTTP Port"*. * I had to assign a different port for those because the default port was in use, so I first had to remove "Web Interface HTTP Port" and readd it in order to change to container's port value too. Also the appdata config doesn't work, probably due to some changes after new versions of NIFI and I couldn't figure out how to solve that...

Oops, I missed that. It never occurred to me to click on a container's name. 🤦‍♂️Thank you.

I'm waiting for this as well, because the Node-RED container's .npm folder is giving me an error during .tar creation. [11.05.2023 18:13:10][NodeRed][debug] Backup NodeRed - Container Volumeinfo: Array ( [0] => /mnt/user/appdata/nodered/:/data:rw ) [11.05.2023 18:13:10][NodeRed][debug] usorted volumes: Array ( [0] => /mnt/user/appdata/nodered ) [11.05.2023 18:13:10][NodeRed][debug] Should NOT backup ext volumes, sanitizing them... [11.05.2023 18:13:10][NodeRed][debug] Volume '/mnt/user/appdata/nodered' IS within AppdataPath '/mnt/user/appdata'! [11.05.2023 18:13:10][NodeRed][info] Calculated volumes to back up: /mnt/user/appdata/nodered [11.05.2023 18:13:10][NodeRed][debug] Target archive: /mnt/user/AppdataBackup/ab_20230511_180314/NodeRed.tar.gz [11.05.2023 18:13:10][NodeRed][debug] Generated tar command: -c -P -z -f '/mnt/user/AppdataBackup/ab_20230511_180314/NodeRed.tar.gz' '/mnt/user/appdata/nodered' [11.05.2023 18:13:10][NodeRed][info] Backing up NodeRed... [11.05.2023 18:13:12][NodeRed][debug] Tar out: tar: /mnt/user/appdata/nodered/.npm/_cacache/content-v2/sha512/26/a3/bbcd36fcc736ca7c1a8f25c3b700af59c1f0317606d1c7df4a76cb572a3d92d4fcc1db367841f6fbb031dfecef09eb72909c185cbbdfb322a27091192caa: Read error at byte 0, while reading 3584 bytes: Input/output error; tar: Exiting with failure status due to previous errors [11.05.2023 18:13:12][NodeRed][error] tar creation failed! More output available inside debuglog, maybe. Hopefully ignoring .npm folder would resolve this.