May 14, 20215 yr Author On 5/5/2021 at 4:01 AM, neupsh said: Hi @cheesemarathon, The icon for Oauth Proxy sticks for a while when update it by editing the docker but it keeps loosing it. Looks like the icon url in the template https://raw.githubusercontent.com/oauth2-proxy/oauth2-proxy/master/docs/logos/OAuth2_Proxy_icon.png has moved and is now https://github.com/oauth2-proxy/oauth2-proxy/raw/master/docs/static/img/logos/OAuth2_Proxy_icon.png can you please update the template to include it? Apologies if you have already updated it and I am probably somehow still on old template. In that case can you suggest how to update it Thanks. Updated!
May 14, 20215 yr Author 2 hours ago, Mr_Jay84 said: Anyone know what this means? Error: ER_BAD_FIELD_ERROR: Unknown column 'description' in 'field list' What is producing this error?
June 18, 20215 yr On 4/29/2021 at 12:27 PM, cheesemarathon said: Thanks for the update! @hmoney007 try frankman's suggestion. This worked perfectly using the adminer container to drop the two tables. Thanks I still think a monolithic container including mariaDB would be nifty for ghost
July 2, 20215 yr On 5/14/2021 at 7:00 PM, cheesemarathon said: What is producing this error? It's from the Ghost container. I was advised on the Ghost forum to perform this... https://ghost.org/docs/faq/misconfigured-mysql-database/ However I still have no idea how to turn off the ANSI quotes. All the guides online tell you how to turn it on, not off
July 20, 20214 yr Hello, Can someone post screenshots, tutorials, etc. of how they got this to work? I was able to clear the original issue: WARNING: MINIO_ACCESS_KEY and MINIO_SECRET_KEY are deprecated. Please use MINIO_ROOT_USER and MINIO_ROOT_PASSWORD No just need to figure out the following: WARNING: Console endpoint is listening on a dynamic port (34921), please use --console-address ":PORT" to choose a static port. Any help is sincerely approciated!
July 20, 20214 yr minio stop working WARNING: MINIO_ACCESS_KEY and MINIO_SECRET_KEY are deprecated. Please use MINIO_ROOT_USER and MINIO_ROOT_PASSWORD API: http://172.17.0.13:9000 http://127.0.0.1:9000 Console: http://172.17.0.13:35209 http://127.0.0.1:35209 Documentation: https://docs.min.io WARNING: Console endpoint is listening on a dynamic port (35209), please use --console-address ":PORT" to choose a static port.
July 21, 20214 yr Author Looks like minio have made some changes to their container. I'll read the docs and update the template this evening!
July 22, 20214 yr On 7/21/2021 at 6:49 AM, cheesemarathon said: Looks like minio have made some changes to their container. I'll read the docs and update the template this evening! any fix with this container ?
July 27, 20214 yr Hi all, I hope this is the right place to ask for help, it's related to nginx reverse proxy config for Oauth2_proxy. wasn't sure where else to ask! I have setup Oauth2_proxy with nginx reverse proxy under my swag container, all working fine, however I was setting up individual callback url's for every single app I have running on every single subdomain of my domain. I have now setup a single callback url using redirect_url in Ouath2_proxy's config, but now nginx is not doing the second hop redirect to the original requested url.. anyone know how to get this setup? many thanks in advance! oauth2_proxy and one of my proxy confs below for your reference.
July 27, 20214 yr I updated Minio to the latest version but I'm still having problems connecting I added MINIO_ROOT_PASSWORD: and MINIO_ROOT_USER: since it was telling them it needed them. After relaunching the docker I now get this WARNING: Console endpoint is listening on a dynamic port (46167), please use --console-address ":PORT" to choose a static port.
July 28, 20214 yr 16 hours ago, SolaAesir said: This thread has help for the port issue with the Minio template. this is working, using internal ip or external web address, but now you can not use it with duplicati, since i use duplicati (on my devices)+minio for backup, now you can not create a connection you get "Failed to connect: 'doctype' is an unexpected token. The expected token is 'DOCTYPE'. Line 1, position 3.", i'm not sure how to react to this, something was fixed, something else got broken 😷 Edited July 28, 20214 yr by Danuel
July 30, 20214 yr anyone know how to fix this problem ? "Failed to connect: 'doctype' is an unexpected token. The expected token is 'DOCTYPE'. Line 1, position 3." i did try with different client s3 browser, cloudberry, and i get the same problem, i think this is something related to minio
July 31, 20214 yr Danuel, Post your Unraid setting for the Minio container. Here is how I have mine set. The CONSOLE port is now used for Web UI - management. The API port is what is used for client connectivity. Settings I used in Unraid (Advanced view): Reminder, when connecting software to perform backups, etc, (Arq, GoodSync, Cloudberry, etc.) you will connect to the API port. So, if using NGINX Proxy Manager, you would map the connection to 9769 (in the example above).
July 31, 20214 yr 4 hours ago, mfwade said: Danuel, Post your Unraid setting for the Minio container. Here is how I have mine set. The CONSOLE port is now used for Web UI - management. The API port is what is used for client connectivity. Settings I used in Unraid (Advanced view): Reminder, when connecting software to perform backups, etc, (Arq, GoodSync, Cloudberry, etc.) you will connect to the API port. So, if using NGINX Proxy Manager, you would map the connection to 9769 (in the example above). your default template is way different then my, however this is not working, cant start container with either internal ip or external
August 15, 20214 yr Author On 7/31/2021 at 9:15 AM, Danuel said: your default template is way different then my, however this is not working, cant start container with either internal ip or external I have just updated the template for minio. It should fix all the issues of recent.
August 15, 20214 yr Author On 7/27/2021 at 6:23 AM, spacey said: Hi all, I hope this is the right place to ask for help, it's related to nginx reverse proxy config for Oauth2_proxy. wasn't sure where else to ask! I have setup Oauth2_proxy with nginx reverse proxy under my swag container, all working fine, however I was setting up individual callback url's for every single app I have running on every single subdomain of my domain. I have now setup a single callback url using redirect_url in Ouath2_proxy's config, but now nginx is not doing the second hop redirect to the original requested url.. anyone know how to get this setup? many thanks in advance! oauth2_proxy and one of my proxy confs below for your reference. Images have timed out, but here is one of my configs: server { listen 80; server_name app.domain.com; return 301 https://$server_name$request_uri; } server { listen 443 ssl; server_name app.domain.com; ssl_certificate /config/keys/letsencrypt/fullchain.pem; ssl_certificate_key /config/keys/letsencrypt/privkey.pem; ssl_prefer_server_ciphers on; add_header Strict-Transport-Security max-age=2592000; location /oauth2/ { proxy_pass http://192.168.1.41:4180; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Scheme $scheme; proxy_set_header X-Auth-Request-Redirect $request_uri; } location = /oauth2/auth { proxy_pass http://192.168.1.41:4180; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Scheme $scheme; # nginx auth_request includes headers but not body proxy_set_header Content-Length ""; proxy_pass_request_body off; } location / { auth_request /oauth2/auth; error_page 401 = /oauth2/sign_in; # pass information via X-User and X-Email headers to backend, # requires running with --set-xauthrequest flag auth_request_set $user $upstream_http_x_auth_request_user; auth_request_set $email $upstream_http_x_auth_request_email; proxy_set_header X-User $user; proxy_set_header X-Email $email; # if you enabled --cookie-refresh, this is needed for it to work with auth_request auth_request_set $auth_cookie $upstream_http_set_cookie; add_header Set-Cookie $auth_cookie; include /config/nginx/proxy.conf; add_header X-Frame-Options SAMEORIGIN; proxy_pass http://192.168.1.41:9080; } }
August 19, 20214 yr After the latest update the Minio container cannot start. I get the following error: ERROR Unable to validate credentials inherited from the shell environment: Invalid credentials > Please provide correct credentials HINT: Access key length should be at least 3, and secret key length at least 8 characters
August 25, 20214 yr Looks like I am not the only one. I can no longer connect to Minio from Arq or duplicacy (CLI). I can still log into the Minio Web UI after having set the root username and password. It does show the previous buckets and such, so no data is lost. When trying to connect from Arq, I get Quote The Access Key Id you provided does not exist in our records From duplicacy Quote The storage has not been initialized Mind you, no changes have been made and the access and secret key are the same as always. I changed docker network type to 'Host' to get access to the GUI working again. Any suggestions about what to try next would be greatly appreciated. This used to work so well, it'd be a real bummer if I had to move to a different backup system:( Thanks
August 25, 20214 yr Author 12 minutes ago, langrock said: Looks like I am not the only one. I can no longer connect to Minio from Arq or duplicacy (CLI). I can still log into the Minio Web UI after having set the root username and password. It does show the previous buckets and such, so no data is lost. When trying to connect from Arq, I get From duplicacy Mind you, no changes have been made and the access and secret key are the same as always. I changed docker network type to 'Host' to get access to the GUI working again. Any suggestions about what to try next would be greatly appreciated. This used to work so well, it'd be a real bummer if I had to move to a different backup system:( Thanks I’ll have a poke in my system tonight as I haven’t updated mine yet. I did make a change to the template to fall inline with changes minio made to the env variables so maybe I cocked that up. Could you send a screenshot of your minio docker setup page in the unbraid ui? Thanks
August 25, 20214 yr Thanks for looking into this. Would be super if this could be resolved. I am wondering if the container actually uses the as-defined access and secret keys. Screenshot attached. Please let me know if there's anything I can help with or if you see anything I should change about the configuration. Thanks
August 25, 20214 yr Author 4 hours ago, langrock said: Thanks for looking into this. Would be super if this could be resolved. I am wondering if the container actually uses the as-defined access and secret keys. Screenshot attached. Please let me know if there's anything I can help with or if you see anything I should change about the configuration. Thanks Easy fix. You're using the env variables that minio has depreciated. I updated the template but they don't seem to have pulled through to you. Remove your container and create it again from community apps. Just don't delete your minio appdata as well!!!! @pervel This should also fix your issue. I have just done the above as well and had no issues. Just make sure to fill in your same user and password as before.
August 26, 20214 yr Fantastic, works again as advertised both for Arq and Duplicacity. Nice feeling to have the backup running once again!
August 28, 20214 yr I'm a bit confused if both MINIO_ACCESS_KEY and MINIO_SECRET_KEY have been depreciated. How do you authenticate when you're connecting from a minio client since they require the access key and secret key? I'm using restic under windows to backup to unraid minio but you can't connect unless you have both the access and secret key, same for FreeNAS since their cloud task (S3 in my case) requires both to authenticate Edited August 28, 20214 yr by sickb0y
August 28, 20214 yr 14 minutes ago, sickb0y said: I'm a bit confused if both MINIO_ACCESS_KEY and MINIO_SECRET_KEY have been depreciated. How do you authenticate when you're connecting from a minio client since they require the access key and secret key? I'm using restic under windows to backup to unraid minio but you can't connect unless you have both the access and secret key, same for FreeNAS since their cloud task (S3 in my case) requires both to authenticate Those two variables still exist. What appears to be gone is the separate key pair used to access the web GUI. Right now it defaults to the ROOT access and secret key. You can define users and group within the web UI, though, which may then also allow those users with their separate keys to back up to the server, but I haven't tried that, yet. There's probably some document that explains how to generate compatible keys in case these need to fulfill certain requirements.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.