Cloudron Forum

I was able to resolve this. I created a subaccount API key that I used for authentication before generating a secret key for the primary API key (by default Mailjet creates a key but not a secret for that key, which is a manual action). Now I just generated a secret key for the primary API key and used this instead of the subaccount key and it worked.

Hey, re-using this thread as I am having some issues setting up mailjet as a relay mail provider.

I followed Mailjets instructions to set up SPF and DKIM records and validated the domain, everything looked good. Unfortunately triggering a test email does not deliver it even though the event log for mail says it was delivered. An email from Vaultwarden was delivered, though it was sent to an email address from the same domain. The Mailjet analytics dashboard says 0 delivered emails. Would be great if anybody can point me at a potential solution.

I created a new subaccount API key in Mailjet and used the API key as the username and the Secret key as the password in Cloudron's relay settings.

• Main Page: https://latitude.so/
• Git: https://github.com/latitude-dev/latitude-llm
• Licence: LGPL-3.0
• Dockerfile: Jein - docker-compose: https://github.com/latitude-dev/latitude-llm/blob/main/docker-compose.yml
• Demo: /

• Summary:
  Latitude is designed for cross-functional teams, enabling collaboration between developers, product managers, and domain experts throughout the entire AI development process:
  • Design and version prompts collaboratively
  • Test iterations in an interactive playground
  • Evaluate and improve prompts systematically
  • Deploy prompts as API endpoints
  • Monitor performance with automatic logging

• Notes: Given that the right prompt can make a big difference in efficiency and LLM output quality, this is a quite useful tool. Though I'm not sure how easy it would be to package for Cloudron since the Docker compose file looks pretty complex with many services.

• Alternative to: Anthropic Workbench
• Screenshots:
  

@firmansi Is this also true for the first user that logs in via Cloudron OpenID or only through the create account form?

This app still seems to be actively developed. Might be nice to have an alternative to Vaultwarden.

• Main Page: https://www.onyx.app/
• Git: https://github.com/onyx-dot-app/onyx
• Licence: MIT Expat for Community Edition, custom license for Enterprise Edition
• Docker: Yes (docs here)
• Demo: n/a

• Summary: Onyx (formerly Danswer) is the AI platform connected to your company's docs, apps, and people. Onyx provides a feature rich Chat interface and plugs into any LLM of your choice. Keep knowledge and access controls sync-ed across over 40 connectors like Google Drive, Slack, Confluence, Salesforce, etc. Create custom AI agents with unique prompts, knowledge, and actions that the agents can take.

• Notes: While I'm personally a bit sceptical about the quality of results from an AI assistant that has access to all your data sources, it's still great to see an open source (with enterprise edition) tool like this, especially for small businesses. The company raised 10M in March 25 so good chances they will be around for a bit.

• Screenshots:
  
  

Just wanted to bump this as the project still seems to be under active development. They now offer a community edition freely available under the MIT Expat license, as well as a paid enterprise edition with additional features. The project was also rebranded under onyx.app.

From the installation notes, it seems like a free copy needs to be purchased in order to receive a shell command that will install docker and then pull the latest Writebook docker image and go through an installation process.

IMPORTANT NOTE: Do not give this install command out to anyone, or share it on the public internet. It is personalized to you, and the license is tied back to you. Your personalized purchase token can be found in the email you received after you downloaded Writebook

The way Writebook is currently distributed, I don't think makes it possible to be packaged for Cloudron unfortunately.

HeyForm is an open-source form builder that allows anyone to create engaging conversational forms for surveys, questionnaires, quizzes, and polls. No coding skills required.

Features

• License: GPLv3
• Versatile Inputs: Up to 40+ form fields supported
• Logic: Conditional logic and URL redirections for dynamic, adaptable forms
• Integrations: Connect with webhooks, analytics, marketing platforms, and tools like Zapier
• Analytics: Detailed analytics, including drop-off rates and completion rates

Stack

• Mongodb
• Redis

This was open sourced in the last week and posted to Hacker News today. Would be great to have another alternative to Typebot and the somewhat old behemoth LimeSurvey for creating online forms.

Thanks girish. I tried to curl other sites and that worked fine as well. Also from my local computer curling api.cloudron.io works fine. I then deleted the server and set up a fresh server and tried the curl command first as you suggested. Same issue.

After that I deleted the server again and set up a new server that also has a IPv4 address instead of IPv6 only. This time the curl command to api.cloudron.io worked and the setup script is currently running just fine ¯_(ツ)_/¯ .

@girish

The setup is basically this, the cheapest Hetzner VPS with a fresh Ubuntu 22.04.3 install. Didn't do anything special, just ssh'd in and ran the three install commands from Cloudrons homepage.

I tried running both of the commands, the first one fails, the second one works:

root@ubuntu-2gb-nbg1-1:~# curl https://api.cloudron.io/api/v1/releases
curl: (7) Couldn't connect to server
root@ubuntu-2gb-nbg1-1:~# host api.cloudron.io
api.cloudron.io has address 165.227.67.76

I am getting the same error message on a fresh Hetzner VPS Ubuntu 22.04.3 install.

=> Updating apt and installing script dependencies
=> Validating setup token
=> Checking version
Failed to get release information

When I look at the logs I get the following output:

root@ubuntu-2gb-nbg1-1:~# cat /var/log/cloudron-setup.log
Running cloudron-setup with args : --
Hit:1 https://mirror.hetzner.com/ubuntu/packages jammy InRelease
Hit:2 https://mirror.hetzner.com/ubuntu/packages jammy-updates InRelease
Hit:3 https://mirror.hetzner.com/ubuntu/packages jammy-backports InRelease
Hit:4 https://mirror.hetzner.com/ubuntu/security jammy-security InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
curl is already the newest version (7.81.0-1ubuntu1.15).
python3 is already the newest version (3.10.6-1~22.04).
software-properties-common is already the newest version (0.99.22.9).
ubuntu-standard is already the newest version (1.481.1).
0 upgraded, 0 newly installed, 0 to remove and 36 not upgraded.

Anybody has any ideas what the problem might be? Not sure if it makes a difference but the server only has an IPv6 address.

Ok, no worries, thank you for confirming!

Hi,

I wanted to restore Cloudron from a backup but in the setup wizard under "Domain Setup" mindlessly filled in the DNS information and clicked next instead of clicking on "Looking to restore".

Now I'm on the "Welcome to Cloudron" page to set up an admin account without any apparent way to go back to the previous step in the setup.

I know this is probably not a common use-case but as far as I understand I will have to re-install Ubuntu on the VPS server and then download and re-install Cloudron again, which is maybe around half an hour I would save if there was such a button

Is there any way to reset the setup, or go to the restore page via direct link?

I'm currently doing the opposite (migrating data from non-Cloudron to Cloudron environment) but I assume it's similar in ways @girish described so just wanted to mention some caveats for people trying this:

1. It's not possible (or at least not trivially possible) to migrate your users. The Vaultwarden docker image uses sqlite while Cloudron uses mysql. The org that I'm trying to migrate has less than 30 users so I'm ok with having to re-invite everyone to the new instance. But if you're trying to migrate a bigger Vaultwarden installation, you'll either have to figure out how to transfer the users between mysql and the sqlite database, or everyone has to create a new account.

2. File attachments have to be copied manually. You can't just scp the attachments folder from one server to the other, this means every attachment has to be downloaded manually through the gui and then uploaded again to the new instance.

Exporting and importing the vault itself was a matter of exporting a json file and then importing it in the new vault. Took less than 5 min.

Ok, thank you!

Hello, I am thinking about using surfer to host a docusaurus site. As far as I understand it's not possible at the moment to protect docs.example.com for let's say all my Cloudron users, and docs.example.com/secret-docs for a specific sub-group of users.

Is this something that could be added as a feature to surfer?

I'm new to Cloudron so I'm not sure what the best workaround would be for this use case.

Hi @potemkin_ai, it sounds like you want to cancel your subscription. Keep in mind that once you cancel your subscription, your apps will keep running but will not receive any more updates.

I just checked up on this project on Github and even though I couldn't find an official statement from the maintainer, two things point towards it being abandoned.

1. There has only been one commit since April 2023, which only updated the readme to
2. Make visitors aware that "Chatbot UI 2.0 is out as an updated, hosted product!"

There is a Github issue that contains a tweet from the maintainer that promises open sourcing "next week" but next week would have been mid August 2023 and so far nothing has happend.

@jdaviescoates said in Just saying hi!:

Why did you do this?

I actually didn't really think about it too much, just a common practice to lock down the root user as @BrutalBirdie mentioned .

@BrutalBirdie

Yes, basically I ran adduser cloudron, followed by usermod -aG sudo cloudron, that was it. But yes, it's just on a small VPS server I set up to test things, I will probably move Cloudron over to a fresh install and bigger server in a couple of weeks so it doesn't really matter, just thought I'd mention it as I thought it was unexpected.