Hey team 👋 Following-up on https://feedback.ultra.cc/p/autoscan-is-depreciated-can-it-be-replaced-by-autopulse Would it be possible to update the docs to reflect this Change? Pages to update: https://docs.ultra.cc/unofficial-application-installers/autoscan https://docs.ultra.cc/unofficial-application-installers Thanks team!
Hey team 👋 The text on this is quite difficult to read, the title and date fields are fine, but the main text is difficult to read. https://status.ultra.cc/status/sites-servers also to note that the notification are repeated, although they are slightly different (looking at the created time) the text is the same.
In the Generic Software Installation page the “here” link loads to a 404 error. Go to https://docs.ultra.cc/unofficial-application-installers/generic-software-installation Impacted Section: “While selecting a port for your custom application, select one within the port range assigned to your service; do NOT use the default port the application suggests. It is strictly prohibited to use ports outside of your range. More info can be found here.” Click the “here” link, next page 404’s Link should point to https://docs.ultra.cc/unofficial-ssh-utilities/assigned-ports-command secondary piece of feedback. Having completed the process I absolutely missed this overall update above 😂 the first time trying it, might be worth adding the commands into the page itself, but I’ll leave that up to you.
The list item for wireguards docs-button directs users to a 404 page: https://docs.ultra.cc/applications/wireguard-%28vpn%29 instead of the valid documentation page: https://docs.ultra.cc/applications/wireguard ## Steps reproduce: Go to the control panel as a signed in user. Open either “Apps” or “Installers“ tab for a service, depending on if wireguard is installed. Find the row for wireguard in the table and click docs button. Note: Bug might not be present in dev environment since local file paths can include “( )“ but those characters are replaced when url-encoded. ## Cause (I think): Front end js helper function hardcodes a custom slug for a few docs-urls: function modifyDocsName(appName) { // ... } else if (appName === 'WireGuard') { return 'wireguard-%28vpn%29'; } //... } Used here: Docs
As per title, using something like app-qui install in the command line leads to the app not popping up in the WebUI. My situation is as follows: the graphical installer for qui failed without an error for me and it didn’t output any troubleshooting information. I decided to try the command line. The command line worked without issue, and now I’m stuck with qui not popping up in the command line. I am aware https://feedback.ultra.cc/p/bug-version-number-of-installed-apps-different-when-updated-via is a thing, but this seems to be a slightly different/more severe issue, since you may or may not have error checking for this and this may corrupt the app state if the GUI installer is not aware of the installation. Also, since the CLI is known to be funky, would it be possible to at least add a: echo “Installing/updating programs using CLI may cause issues with the WebUI” to the script, or to --help ?
Following the instructions listed on https://docs.ultra.cc/community/cross-seed while The Lounge is installed leads to a broken cross-seed installation. Investigating closer, it seems to be due to that both write a node-related variable into .bashrc, which leads cross-seed to use The Lounge’s copy of node. This causes a versioning conflict with one of cross-seed’s dependencies. I’m not sure what the consequences would be of installing cross-seed first and then installing The Lounge, but I presume it wouldn’t be good. Though I realize the cross-seed installer is not officially supported and this probably won’t be fixed, could we at least put a specific disclaimer about this in the install guide?
The Audiobookshelf app is not upgrading past 2.19.3 when the latest release is currently 2.32.1.
Bug: App versions are displayed for installed apps in User CP > Services > Apps. When apps are updated with the binary updaters eg. app-radarr upgrade the new / current version numbers are not updated in the webUI of the control panel. Request: the webUI consistently shows the current version number of app deployed, regardless of deployment method (webUI / app-* binary). Thank you.
Hi all, After trying to update flaresolverr to pr-1282, the version is still 3.3.21. There's no error during the update, did I miss something? Outputs: #Upgrade ethost@comet:~$ app-flaresolverr upgrade --version 'pr-1282' {"data": {"port": 15961, "version": "pr-1282", "api_url": "http://172.17.0.1:15961"}, "result": true} #After upgrade ethost@comet:~$ app-flaresolverr --version app-flaresolverr 2024.05.02 ethost@comet:~$ curl http://172.17.0.1:15961 {"msg": "FlareSolverr is ready!", "version": "3.3.21", "userAgent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36"}
After installing Simkl Tracker plugin & restarting the Emby app, I tried to login with Simkl tracker plugin. It throwed this error. Error: Solution that worked for me: I connected to my usbx vpn and logged into my Emby via usbx's local IP address & port (found in network tab of emby server dashboard) Then I successfully logged in to my Simkl account using the Simkl Tracker plugin. I wonder why it throws error via usbx URL, because I didn't face any issue while connecting to my Trakt account via Trakt plugin in Emby.
To do this yourself, just install bazarr and set up sonarr and radarr together using the docs, and usbx.me. You will be able to see that Movies has the "live" tag, while Series doesn't. To fix this, you just have to add the websocket fields to get it working. This should be included in the configs by default. proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $http_connection;
Currently, the commands returns the date of (I think?) latest installed version (ex with Sonarr: it returns app-sonarr 2023.11.03) instead of the number of the version.
Plex addresses are showing invalid certificate. The address is usually "lwXXX-direct.usbx.me" but the certificate is for "lwXXX.usbx.me". Invalid certificates gives us error on some TVs when setting up plex.
There is currently a guide to fix Plex databases. It does not work with current versions of Plex as they use their own SQLite binary