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.

aptalca

Community Developer
  • Joined

  • Last visited

Everything posted by aptalca

  1. Check your site config. You probably have a redirect somewhere
  2. What php.ini did you create? Only modify the php local and restart. You don't need anything else
  3. ?? You didn't mention you already made changes to enable reverse proxy. That requires a whole another set of troubleshooting methods. Https is not a valid option for validation. Check the docs
  4. That was an annoying forced change by letsencrypt done to reduce their server load at peak times. I guess they forgot that many people have scripts that are not run by cron. We pushed an emergency update last night to remove cert renewal during container start
  5. Is wordpress set up in the letsencrypt container or are you reverse proxying? I have them set to 64MB the same way and it works
  6. With letsencrypt, you're trying the https address, right? Log suggests nginx is started and there are no errors. What happens when you try to connect?
  7. Make sure that your ip is set correctly on your dns provider and that there is a cname created and set up for the "server" subdomain. If all looks good, you can try stopping the letsencrypt container, create an nginx container with the same exact port mapping, and see if you can reach it through the domain and ports 80 and 443
  8. Ipv6 is not supported in this image
  9. I think you mean proxy and not redirect (they have very different meanings for webservers) If you post your config we'll take a look
  10. Use only lowercase in container names otherwise nginx can't resolve them
  11. That's a dns hostname resolution thing. Not nginx's fault. Use all lowercase in container names or define a network alias for the container
  12. First set it to the regular bridge and set up your port forwards if you like. Save and exit. Go into the container settings one more time, change it to proxynet, don't enter an ip and hit save. Unraid doesn't recognize your proxynet as a custom bridge network (assumes it is macvlan) so if you try to change port mappings after selecting proxynet, unraid won't do it properly.
  13. Not sure how duo works but ldap auth is already included. For radius, there is no alpine package in the repo.
  14. Sure, you just use the ip of the vm in the proxy_pass directive
  15. Reverse proxy it and then use your domain name in that field
  16. Glad to hear it works now
  17. It sounds like your duckdns.conf is messed up somehow. It is only supposed to contain two lines, and two items each, separated by an equal sign, no spaces. Check to see if it's the correct format. You can also pm me the contents (I believe duckdns lets you recreate the token) Also, are there any special characters in your token other than hyphen?
  18. Actually, it was something you did within the last 2-3 months. The update only caused a forced validation due to expiring certs, and that process failed. Check your port forwarding on your router

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.