Thanks, @james We have already updated our API call. Our point was more that changes like this — especially breaking changes — should ideally be documented. We weren’t able to find any documentation mentioning this change.
Additionally, in this specific case, it’s not clear to us why the field suddenly needs to be mandatory. From our perspective, it seems rather obsolete.
Since the update to Cloudron 9.0.9, our previously working API requests for creating a mailbox no longer function.
Our script used to run without any issues, but now the endpoint /api/v1/mail/boxes returns the following error:
400 - {
"status": "Bad Request",
"message": "enablePop3 must be a boolean"
}
In the API documentation
(https://docs.cloudron.io/api.html#tag/Mail/operation/addMailbox)
the field enablePop3 is not listed.
As a result, older requests never included this field and are now invalid.
From our perspective, it would make sense for this field to be optional and—if omitted—automatically interpreted as false. This would maintain backward compatibility for existing integrations.
Additionally, is there a changelog available for recent API changes?
it works. thank you.
@marylou i tried to set these today and had no luck. were you able to resolve the issue?
Somehow - no idea why, i didn't do anything new - yesterday increasing the upload limit to 150MB was sucessfully saved. Still i can't activate avif, heic and mov support in the media settings, but for now i am fine with that.
@james i followed the instructions in thread mentioned
(and i think you updated the docs and links in there)
Hello,
i am trying to increase the upload size in the admin settings as described here:
https://forum.cloudron.io/topic/10096/cannot-increase-max-upload-size
Every time i try to save those settings in the admin panel they get reset to the former values on reload - therefor this seems to me like the settings bug from here reappeared: https://forum.cloudron.io/topic/11247/delete-server-rules-button-does-not-delete-rule/32
can anyone confirm this behavior or is there any hint what i can do? i tried the cache clearing commands from the docks, edited the php.ini and the env.production file, but every time i enter the admin settings i have an upload size of max 50MB. Also enabling other video formats in the same settings-page is reset.
Running Pixelfed 0.12.5 on Cloudrom v8.3.2 (Ubuntu 22.04.4 LTS).
I keep getting this error. i reinstall now für the third time. As we don't work with the online office on a regular basis, i can't tell how long it works before getting into this error.
i managed to install sftpgo from the @BrutalBirdie repository. while the server kept on working the webinterface is banned - restarting doesn't resolve this.
{"level":"debug","time":"2025-02-24T12:24:20.019","sender":"dataprovider_postgresql","message":"ban time updated for ip \"172.18.0.1\", increment (minutes): 15"}
and to be honest i don't get how to update to the mentioned versions above 0.0.9 as they don't seem to be available?
@joseph reinstalling solved the issue. For now it runs normal.
@nebulon yes. restarted it several times.
only https://office.domain.de/hosting/discovery throws the error - https://office.domain.de/ is working and cloudron states the app is healthy and responsive.
Getting the same error. Nextcloud states:
Failed to connect to the remote server: Server error: `GET https://office.domain.de/hosting/discovery` resulted in a `502 Bad Gateway` response: <!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <meta name="viewport" content="user-scalable=no, initial- (truncated...)
If i call the URL in browser i also get the cloudron error page. Restarting the app doesn't change this behaviour.
the app log of collabora says:
Feb 13 16:20:16 2025/02/13 15:20:16 [error] 21#21: *128 connect() failed (111: Unknown error) while connecting to upstream, client: 172.18.0.1, server: , request: "GET /hosting/capabilities HTTP/1.1", upstream: "http://127.0.0.1:9980/hosting/capabilities", host: "office.domain.de"
Feb 13 16:20:16 2025/02/13 15:20:16 [warn] 21#21: *128 upstream server temporarily disabled while connecting to upstream, client: 172.18.0.1, server: , request: "GET /hosting/capabilities HTTP/1.1", upstream: "http://127.0.0.1:9980/hosting/capabilities", host: "office.domain.de"
We are considering using documize community as knowledge base. As we would need some features of the community+ version. Is there a way to use it on cloudron?
@girish i had contact to @fre2mansur. According to him it's necessary for the script to have the plugin folder writeable. i made this as shown in the screenshots. i don't have any knowledge about the structure the cloudron app establishes - but i see that the plugin folder exists there in /app/pkg/plugins (readonly) and /app/data/plugins (where i can upload the files to). maybe this causes the problem?
On https://devmansur.me/ there is a video with the installation instructions. I understand that the devmansur theme is installed the way any other plugin would be installed and you dont have to alter the core files.
In my lamp stack i just uploaded the ost-dashboard folder and activated it.
I try to install the theme plugin by devmansur. Using Osticket in Lamp it works as described: upload in plugins folder and activate. In the cloudron osticket app i uploaded it via file manager, can install it via admin panel but that don't seems to work as the theme stays the original one.
Osticket-App:
LAMP:
I don't find information whether plugins can be used in the cloudron osticket-app - just tried it that way. Thanks in advance.
hello @nebulon ,
i see you updated the package to 0.12.1. I made a fresh install of the app. Still i can't get the admin panel to work. Any changes in settings are dropped immediately. Is this broken only on cloudron installs? Pixelfed seems to be used widely. Is there some kind of workaround? Editing the env.production file?
Is @dansup aware that the issue persists?