Is there any change log published anywhere for new version of MiroTalk? It would be useful.
@MiroTalk do you publish any?
Is there any change log published anywhere for new version of MiroTalk? It would be useful.
@MiroTalk do you publish any?
@firmansi And I guess that would get solved if you ran your instance on a more local server...one more reason for Grist on Cloudron
@jdaviescoates said in How to setup Hetzner Storage Box using SSHFS:
@avatar1024: you've mentioned previously that you've had issues restoring from SSHFS - is that still the case?
I've had no more issue restoring using sshfs. I had issues (getting the same error message as you) when using specific ssh key pairs. rsa keys have been more reliable than Ed25519 keys, and do not protect your key with a password. Then it should work like a charm. See my post here: https://forum.cloudron.io/post/86213
Thank you for this, I've started looking into how to pull all of the logs and will submit as soon as possible.
One thing I can say is that it definitely seems to happen a lot more when hotspotting from my phone on mobile network but also happens with stable home WiFi. Trying other tools like zoom, teams or the public jitsi I have no issues whatsoever.
Also I can only make it work with Firefox, with chromium (ungoogled) I get no camera and other problems (whereas all other platforms perform better on Chromium).
So it'd say for me the tool in it's current implementation is not yet ready for production / environment. Even the public jitsi is way more stable.
I keep hitting this with MiroTalk SFU and so I have to enter the room many times during a meeting. It's me who set-up the room but strangly other participants in the meeting did not have the problem and could carry on with the meeting while I was dropping out.
Hello, it looks like Noco supports authentication with OIDC (Auth0). Does that mean it's now possible to have a package that uses Cloudron users?
Hello, I wonder, is anyone is working on this? Seems like grist is ahead of the others regarding what it offers in the self hosted version.
@girish said in What's coming in 9.0 (was 8.0):
@avatar1024 we have to revisit this when we plan for 9.0 . currently, we focus on 8.0 - https://forum.cloudron.io/topic/11531/what-s-coming-in-8-0
Sure, I just wondered as it wasn't listed in the list at the top of this thread.
Sorry I'm sure this has been discussed but has the plan been dropped to have a unified dashboard across several instances?
@MiroTalk said in Use Cloudron Logins for host protected settings:
Not a behaviour intended! I'm considering a refinement where guests are only allowed to join specified rooms that have already been created by authenticated users. This approach might offer better control and security. Will be released in the next version.
I thought that might be the case. Though as I mentioned the behaviour is achieved though by setting "protected: true" in the config.js combined with OICD. It just feels like if OICD is enabled then it shouldn't be possible for guests to create rooms so the setting shouldn't be necessary.
Thanks for this. Just to make it clear to people, in order to obtain the behaviour in 2, you still need to modify the config.js file and enable authentication (protected: true). Otherwise, while guest cannot enter the app base domain without a login, they can still create rooms freely by creating a url: mirotalkappprefix.mydomain.com/join/roomname
@MiroTalk is that behaviour intended?
@nebulon perhaps the "protected: true" should be enable by default in the package with OICD as I imagine this is the behaviour most users expect if they want authentication?
@girish ooops, thank you Girish, I had somehow missed that it worked with that function.
2024...and this is still a problem. Is there still no workaround to run a cron job?
@nebulon thank you for this! I had this same issue for months and your fix seems to work. Something must have changed with NC28 as other (non cloudron) users have experienced and reported this in NC github. In fact I hadn't even thought of reporting it here as I thought it was not cloudron related. I wonders if what you did to the NC cloudron package could be helpful to others...?
@MiroTalk said in participants have to authenticate even with user_auth: false:
By default, this endpoint is set to MiroTalk WEB but disabled. However, you have the flexibility to modify this endpoint to connect to your own database.
@staff is it technically feasible to connect MiroTalk SFU to the Cloudron users database for authentication? Manually creating user and and password in the config file is not very convenient and doesn't feel very secure.
@avatar1024 Just to add that the issue is also there with p2p version.
@girish said in AVX Support in your VPS/Server:
Curiously, in the order sheet, it still says "Root server". Is this the mistake I am making? Is there another page to get some non-avx server?
Nah that is the correct and only page for VPS. I think someone in their team is tripping and mixing shit up with the orders . I wonder, should we tell or not tell them 🤫
@MiroTalk where did you see that?
My Cloudron says:
Also I've done a fresh install of MiroTalk SFU on another server (also Cloudron). It shows the same version number and I hit the same issue.
Just got their response:
"Normally, AVX is not activated on the VPS. I don't know why this was or is the case. If this is the case, you are lucky with the server."
Sounds odd to me...