Taddeusz

@dodgypast If you have your Guacamole container on a custom network you use the container port. Try changing your conf file from 9999 to 8080 and see if it works.

@Fidreus I'll have to take a look at this. I currently don't have any way of ensuring the extensions get loaded in a particular order.

@Fidreus What happens if you add the following to your guacamole.properties file? auth-provider: org.apache.guacamole.auth.openid.OpenIDAuthenticationProvider

I believe you are in the wrong place. This is the support for the Guacamole remote desktop server. It happens to now be part of the Apache Foundation. It specifically has nothing to do with the Apache web server. I can’t help you with that.

@uek2wooF Make sure you're putting your hostname and port in the "PARAMETERS" section and NOT the "GUACAMOLE PROXY PARAMETERS (GUACD)" section.

Basically MakeMKV takes the raw video from a DVD or Blu-ray and puts it into an MKV container. It also lets you choose the audio and subtitle tracks you wish to include.

I would use MakeMKV to convert it.

I have my username and password set. Then I have the Security Mode set to NLA and have Ignore Server Certificate checked. You may also play with some of the performance settings to see if anything improves or makes it worse.

Looks like that’s done with proxy_read_timeout in Nginx. Default is 30.

@Living Legend That looks normal.

Another thing you can do is open the dev tools in Chrome (F12). Then connect to your Windows system. Look at the console and see is there are any errors about websockets. You can look at the Network tab and filter by WS to see if it’s getting websockets communication.

The Docker container is accessed directly through its Tomcat instance. This refers to whatever web server you’re using as a proxy. This only applies if you’re using Apache as your proxy server. The header upgrade I referred to earlier for Nginx accomplishes the same thing, to be able to proxy web sockets. Look in your catalina.out file to make sure websockets isn’t failing. What browser are you using?

@Living Legend Make sure the proxy configuration includes the line to automatically "upgrade" the connection to use websockets. Also recommended is to disable proxy buffering. Insert these into your Nginx conf file for Guacamole and see if they make things work better: proxy_buffering off; proxy_set_header Upgrade $http_upgrade;

I had the same problem. Remove the duplicate one in your subdomain conf file and the warning should go away.

Apache Guacamole 1.1.0 has been pushed out to "latest". Other than the version change the base container is now debian:stable-slim to shave off some size. No database schema changes this time around. Have fun. Especially since this deviates slightly from the official containers in using Tomcat 9 and Java 11. Please let me know if you have any issues.

I'm almost ready to push out 1.1.0. I just want to get some clarification on this. I've added this to the /etc/tomcat9/server.xml file within the Host element. I have my personal container set to use a custom proxy network and I'm just seeing 172.x.x.x addresses. I'm not sure if this would change if my container was set to "bridge". If you'd like to try it out you can change the repository in your container to "jasonbean/guacamole:1.1.0-nomariadb" or "jasonbean/guacamole:1.1.0" depending on which version you're using. I'll wait to change these to "latest" just in case I need to make some changes.

Once you get back in make sure you generate and save backup codes.

If you generated your backup codes you can use one of those to get back into your account.

@OFark What version of Unraid are you running?

I'll look at this. I've had a busy life lately and just haven't had time to sit down and work on it.

I see, I hadn’t read anywhere that’s the reason why it wasn’t working.

Thanks, kind of a $&@&! move there. Had I the time I would. I realize this is the support forum for the LSIO Nextcloud container. Obviously something with it isn’t working quite right. It’s also not apparent that the problems with it and the Community Document Server are reasonably fixable.

I think we need a template for the official Nextcloud Docker container. The problems with the LSIO container may not be reasonably solvable.

That is correct. 1.0.0 was released Jan 8, 2019. There were no new versions until the recent 1.1.0 release over a year later. I currently don’t have a timeline to release an updated container. My family has been rather busy lately and I started a new job in November. Please be patient.

Yes, I have to carve out some time to make it happen.