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.
J
jkammerer
@jkammerer
Posts
-
Endpoint not reachable. reinstallation has helped (https://collabora.example.org/hosting/discovery) -
SFTPGoi 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?
-
Endpoint not reachable. reinstallation has helped (https://collabora.example.org/hosting/discovery)@joseph reinstalling solved the issue. For now it runs normal.
-
Endpoint not reachable. reinstallation has helped (https://collabora.example.org/hosting/discovery)@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. -
Endpoint not reachable. reinstallation has helped (https://collabora.example.org/hosting/discovery)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" -
Community+ also available?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?
-
Responsive Theme@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?
-
Responsive ThemeOn 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. -
Responsive ThemeI 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.
-
Delete server rules button does not delete rule.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?