Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (โ‹ฎ) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Pixbone

Members
  • Joined

  • Last visited

Everything posted by Pixbone

  1. Ok thanks. My problem is that the container doesn't start with any of the options I tried, including the fix options you mentioned. Or I did it wrong. It set Tailscale Serve to No. Is that what you mean by not using it?
  2. Thank you @error311 . I tried all combinations of port mapping, but it seems that even when HTTPS is left blank, Apache 443 still tries to connect. Since the Apache server is not starting for me at all, I have no way to access your link:port address suggestion. I tried to turn off Tailscale serve, hoping it would stop using port 443, but no luck. This is the Docker log: Docker run With Tailscale off, the container is running fine. Do you see any issues with my port setup?
  3. Nice app. Love the demo and excellent developer communication I have seen. Kudos! Looking for a new decent file manager for my media server, and this looks very promising. Unfortunately, I have trouble getting Tailscale to work, which I usually use for all my containers. With tailscale disabled, the container starts fine. (Since I'm doing it remotely, I wasn't able to check local access.) With tailscale turned on (serve) I'm running into the 443 conflict as shown in above screenshot. I tried a few things, including deleting the https port variable, but no luck so far. Any advice on getting Tailscale to work with Filerise? Or is there a better, more/same secure way to remote access?
  4. I rolled back the update and am using this 2 weeks old Repository now: lscr.io/linuxserver/piwigo:amd64-15.6.0-ls308 Piwigo is working normally again, and the Smarty errors are gone. What has changed in the recent updates that causes the Smarty/PHP error? ChatGPT: The errors indicate that your version of Smarty (a templating engine used by Piwigo) is using PHP code that is deprecated in your current PHP version. ๐Ÿ” Root CauseYou're likely running PHP 8.1 or later, where function parameter type declarations must explicitly specify ?Type for nullable parameters, instead of omitting the type and assuming itโ€™s nullable.
  5. Piwigo ran well until recently (I noticed it yesterday). I get a similar, if not the same, error as firebladex. Any idea what has changed? Deprecated: Smarty::_getTemplateId(): Implicitly marking parameter $template as nullable is deprecated, the explicit nullable type must be used instead in /app/www/public/include/smarty/libs/Smarty.class.php on line 1048 Deprecated: Smarty_Internal_Data::getTemplateVars(): Implicitly marking parameter $_ptr as nullable is deprecated, the explicit nullable type must be used instead in /app/www/public/include/smarty/libs/sysplugins/smarty_internal_data.php on line 193 Deprecated: Smarty_Internal_Data::_mergeVars(): Implicitly marking parameter $data as nullable is deprecated, the explicit nullable type must be used instead in /app/www/public/include/smarty/libs/sysplugins/smarty_internal_data.php on line 203 Deprecated: Smarty_Internal_Template::__construct(): Implicitly marking parameter $_parent as nullable is deprecated, the explicit nullable type must be used instead in /app/www/public/include/smarty/libs/sysplugins/smarty_internal_template.php on line 149 Deprecated: Smarty_Resource::source(): Implicitly marking parameter $_template as nullable is deprecated, the explicit nullable type must be used instead in /app/www/public/include/smarty/libs/sysplugins/smarty_resource.php on line 175 Deprecated: Smarty_Resource::source(): Implicitly marking parameter $smarty as nullable is deprecated, the explicit nullable type must be used instead in /app/www/public/include/smarty/libs/sysplugins/smarty_resource.php on line 175 Deprecated: Smarty_Resource::populate(): Implicitly marking parameter $_template as nullable is deprecated, the explicit nullable type must be used instead in /app/www/public/include/smarty/libs/sysplugins/smarty_resource.php on line 199 Deprecated: Smarty_Template_Source::load(): Implicitly marking parameter $_template as nullable is deprecated, the explicit nullable type must be used instead in /app/www/public/include/smarty/libs/sysplugins/smarty_template_source.php on line 158 Deprecated: Smarty_Template_Source::load(): Implicitly marking parameter $smarty as nullable is deprecated, the explicit nullable type must be used instead in /app/www/public/include/smarty/libs/sysplugins/smarty_template_source.php on line 158 Deprecated: Smarty_Internal_Resource_File::populate(): Implicitly marking parameter $_template as nullable is deprecated, the explicit nullable type must be used instead in /app/www/public/include/smarty/libs/sysplugins/smarty_internal_resource_file.php on line 28 Deprecated: Smarty_Internal_Resource_File::buildFilepath(): Implicitly marking parameter $_template as nullable is deprecated, the explicit nullable type must be used instead in /app/www/public/include/smarty/libs/sysplugins/smarty_internal_resource_file.php on line 101 Deprecated: Smarty_Internal_Method_GetTemplateVars::getTemplateVars(): Implicitly marking parameter $_ptr as nullable is deprecated, the explicit nullable type must be used instead in /app/www/public/include/smarty/libs/sysplugins/smarty_internal_method_gettemplatevars.php on line 34 Deprecated: Smarty_Internal_Method_GetTemplateVars::_getVariable(): Implicitly marking parameter $_ptr as nullable is deprecated, the explicit nullable type must be used instead in /app/www/public/include/smarty/libs/sysplugins/smarty_internal_method_gettemplatevars.php on line 87

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions โ†’ Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.