Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
A

ajax

@ajax
About
Posts
3
Topics
3
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Customizing Chatwoot Logos on Cloudron
    A ajax

    Hello

    I'm looking to customize the Chatwoot interface by replacing the default logos with our company's branding.
    I tried uploading the files directly via the console, but I ran into a roadblock due to the read-only file system enforced by the Cloudron installation.

    Has anyone here successfully managed to change the logos in this setup?
    Is there a recommended method or a workaround to achieve this kind of customization?

    Thanks

    Chatwoot

  • Chatwoot SMTP/IMAP Configuration on Cloudron
    A ajax

    Hello,
    I am contacting you to know if it would be possible to have more details than what is available in the Chatwoot Cloudron documentation regarding the setup of SMTP and IMAP messaging.
    The email that is created during the setup of an inbox is not functional (we cannot send emails to it because the domain see-docs.cloudron.io does not exist). We then tried to change it in the terminal via /app/data/env.sh but to no avail.
    Are the ports and IP addresses to be configured during creation specific to Chatwoot or to the external SMTP server?
    Thank you in advance for your response.

    Memos

  • OAuth Issue: Incorrect client_id still used despite environment update
    A ajax

    Hi everyone,

    I'm facing a persistent issue with Google authentication on a self-hosted Chatwoot instance running on Cloudron.

    When I click on "Sign in with Google", the OAuth URL that's generated is still the following:

    https://accounts.google.com/o/oauth2/auth?access_type=offline&client_id=40481950185-vlajho97rkkpavs7f7tahn0c5j36e0d3.apps.googleusercontent.com&prompt=consent&redirect_uri=https%3A%2F%2Fchatwoot.yobbo.bakbit.com%2Fgoogle%2Fcallback&response_type=code&scope=email+profile+https%3A%2F%2Fmail.google.com%2F

    The issue is that this client_id refers to an old OAuth credential, even though I have updated the correct GOOGLE_CLIENT_ID in /app/data/env.sh with a completely different ID.
    I've saved the file and restarted both the services and the app multiple times — but the old ID is still being used.

    Is there some caching or compilation step I might be missing?
    Do I need to recompile Chatwoot or reload something beyond restarting the app?

    Thanks

    Chatwoot
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search