Not sure if cloning is exactly UI-friendly here. The user intention is to add another domain, which is a separate action than cloning. You'd assume you perform an action that is separate from other domains, I'd say.
For backup sites, I am more with you: There it makes more sense to use the same site, but change a detail.
Yes, this is with Porkbun DNS and it happens when I change a location of an app. It would be great if it could show the domain, so that I know where to look, and perhaps it would also be helpful if the domain tab marked that domain, as "invalid API key" is a permanent error anyway.
I host most of my domains in one Porkbun account, but this would work similarly for any other provider. For any new domain I add, I need to find again the API key and secret key and add it. If they ever change, I need to change them for all domains separately.
Idea: Store the secrets separately, and allow the user to change/update them in one place. This would be optional, and the user could still use separate API keys per domain, but I think we can assume that one would want to use the same pair of keys for the same account in Cloudron.
Besides, the values are stored already anyway if they are in use, so this changes only the underlying database structure and the UI.
Following up on this, if it errors out, then maybe the domain menu could show a warning. This is at least where I would expect it.
@girish You wanted to know when this happens again somewhere
I have just seen this error message when updating the location tab of a custom app:
Porkbun DNS error 400 {"status":"ERROR","message":"Invalid API key. (001)"}
This is actually expected, but how do I know which API key is meant here? I'll figure this out for my setup, but perhaps the error message should be clearer.
@archos Did this occur while upgrading from Cloudron 8 into the 9 series?
@james said in Mirotalk - Participants can't see each other 2:
Hello @ekevu123
Can you share where you are hosting your Cloudron?
Netcup, root server
Don't forget, though, that the issue isn't permanent.
@MiroTalk said in Mirotalk - Participants can't see each other 2:
Also make sure that the firewall on your VPS/VDS is not enabled or blocking the required ports. For example, on Amazon EC2, if the inbound security group rules for the necessary RTC ports are not configured, the service will not work...
Thank you! I only let Cloudron handle this.
No, I can't find any pattern, but I have just tested again after a server restart, and the issue persists
I keep having the issue sporadically, which makes it hard to use Mirotalk as a constant video provider without testing the connection before every meeting.
Correct, I have updated all custom apps without a title in the manifest, this solved the issue.
@nebulon Yes, I do - since it was optional, I haven't integrated it everywhere. I'll see that I update the apps then.
style-BG7Zm8Ck.js:1965 TypeError: Cannot read properties of undefined (reading 'toLocaleLowerCase')
at index-CJd8uz05.js:2335:295
at wrappedFn (style-BG7Zm8Ck.js:983:19)
at Array.filter (<anonymous>)
at apply$1 (style-BG7Zm8Ck.js:991:27)
at Proxy.filter (style-BG7Zm8Ck.js:883:12)
at ComputedRefImpl.fn (index-CJd8uz05.js:2331:25)
at refreshComputed (style-BG7Zm8Ck.js:598:29)
at get value (style-BG7Zm8Ck.js:1591:5)
at Proxy.<anonymous> (index-CJd8uz05.js:2521:45)
at renderComponentRoot (style-BG7Zm8Ck.js:6077:16)
I am on Cloudron 9.0.12 and searching apps under "My Apps" stopped working. Under My Apps, when I type something into the search bar, when hitting the second letter, the whole main screen goes blank besides the left side bar. Not blank as in no results found, but blank as in all black with only the sidebar left. Refreshing the page helps, and this is repeatable. Filtering works.
More annoying than critical.
That would indeed explain it, but - and that is probably a question to the Cloudron team - shouldn't Cloudron prevent exactly that?
Thank you, I will try that!
Since I faced the issue temporarily yesterday, but didn't when I tried to reproduce it with my phone, is the explanation that the port I was trying to use for the conversation was temporarily blocked, and restarting the app later re-assigned the port, so it worked again when starting a new conversation?
It has worked again now after changing the port and restarting the app. Does it need to be any port between 25000 and 30000?
@james This issue is back
This has gone back to normal for a few days in a row, indicating the upgrade didn't produce an issue, but probably the hardware infrastructure at Netcup.
Honestly, I didn't try. I didn't find evidence that this was possible, so I assumed it wasn't.
For my needs, I have found a different solution for this now, but maybe this could be helpful to clarify, if it works, then in the docs.