Cloudron Forum

@TheMoodBoardz the app is only setting CORS for very specific routes. See https://github.com/getfider/fider/blob/253556bfb632ab9a7c5d552f1e63c1fb1d7c41b1/app/cmd/routes.go#L42C14-L42C30 . Indeed, I can confirm in my test install that feed.atom and also the favicon have CORS set to '*' . I think the upstream app has to fix CORS (if it supports it) for the post routes.

Great that you managed to get this resolved quickly and thanks for sharing the solution.

Since the last update (v1.85.1), the machine learning do not work: [Nest] 42 - 04/02/2025, 5:28:49 PM ERROR [Microservices:{"id":"73e5da08-c8e7-4d1a-b557-e210f2cb5289"}] Unable to run job handler (faceDetection/face-detection): Error: Machine learning request '{"facial-recognition":{"detection":{"modelName":"buffalo_l","options":{"minScore":0.7}},"recognition":{"modelName":"buffalo_l"}}}' failed for all URLs Apr 02 19:28:49 Error: Machine learning request '{"facial-recognition":{"detection":{"modelName":"buffalo_l","options":{"minScore":0.7}},"recognition":{"modelName":"buffalo_l"}}}' failed for all URLs Apr 02 19:28:49 at MachineLearningRepository.predict (/usr/src/app/dist/repositories/machine-learning.repository.js:98:15) Apr 02 19:28:49 at process.processTicksAndRejections (node:internal/process/task_queues:105:5) Apr 02 19:28:49 at async MachineLearningRepository.detectFaces (/usr/src/app/dist/repositories/machine-learning.repository.js:107:26) Apr 02 19:28:49 at async PersonService.handleDetectFaces (/usr/src/app/dist/services/person.service.js:239:52) Apr 02 19:28:49 at async JobService.onJobStart (/usr/src/app/dist/services/job.service.js:156:28) Apr 02 19:28:49 at async EventRepository.onEvent (/usr/src/app/dist/repositories/event.repository.js:126:13) Apr 02 19:28:49 at async Worker.processJob (/usr/src/app/node_modules/bullmq/dist/cjs/classes/worker.js:394:28) Apr 02 19:28:49 at async Worker.retryIfFailed (/usr/src/app/node_modules/bullmq/dist/cjs/classes/worker.js:581:24) Apr 02 19:28:49 [Nest] 42 - 04/02/2025, 5:28:49 PM WARN [Microservices:MachineLearningRepository] Machine learning request to "http://127.0.0.1:3003" failed: fetch failed If I try to start it from supervisord: Apr 02 19:36:12 2025-04-02 17:36:12,166 INFO spawned: 'machine-learning' with pid 520 Apr 02 19:36:12 warning: `VIRTUAL_ENV=/app/code/venv` does not match the project environment path `.venv` and will be ignored; use `--active` to target the active environment instead Apr 02 19:36:12 error: Failed to install: httpx-0.28.1-py3-none-any.whl (httpx==0.28.1) Apr 02 19:36:12 Caused by: failed to create directory `/app/code/machine-learning/.venv/lib/python3.12/site-packages/httpx`: Read-only file system (os error 30) Apr 02 19:36:12 2025-04-02 17:36:12,247 WARN exited: machine-learning (exit status 2; not expected) Also, I'm not sure if this occurs since the last upgrade: root@2e57dda8-6002-47bd-b15c-be4345bc5a94:/usr/src/app# admin-cli node:internal/modules/cjs/loader:1228 throw err; ^ Error: Cannot find module '/app/code/server/dist/main' at Function._resolveFilename (node:internal/modules/cjs/loader:1225:15) at Function._load (node:internal/modules/cjs/loader:1055:27) at TracingChannel.traceSync (node:diagnostics_channel:322:14) at wrapModuleLoad (node:internal/modules/cjs/loader:220:24) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:170:5) at node:internal/main/run_main_module:36:49 { code: 'MODULE_NOT_FOUND', requireStack: [] } Node.js v22.14.0

Hey @brutalbirdie is there a specific reason why # Where will social media icons be saved - local or cloudflare. STORAGE_PROVIDER="local" is set in the start.sh? I'd like to test this with Cloudflare R2

Ok, I have managed to get it working... it seems that the type of "openid-jwks-endpoint" I was using was not correct.

It is currently not on our list, given the penpot installation count we see and that being quite the edge case on top which needs extra maintenance on our side. We will keep it in mind for when we have free resources to tackle that.

@TheMoodBoardz YW dude

@girish So after running a few tests it seems that Traccar does not like the domain to have a "/" at the end, no error logs to support this, but it does track with what was happening - typically my SSO system will want this, so I have made some changes, and it is all working now.

AnythingLLM has had enormous improvements since it was first requested by @TheMoodBoardz In particular, support for agents and RAG has been advanced to try and keep up with the huge demand in this area. Installing AnythingLLM on GNU+Linux now automatically installs Ollama, too. Here is a summary of the main advances. If you want to make RAG and ai agents easier, AnythingLLM would be a great application to support. Comparison between v1.0Based.0 and v1.9.0 of AnythingLLM, here are the most significant changes categorized into key areas: Agent System Overhaul Complete redesign of the agent experience with real-time streaming tool calls Agents can now download and ingest web files (PDF, Excel, CSV) during conversations All providers and models support agentic streaming capabilities Local LLM Integration Added Microsoft Foundry Local integration for Windows/MacOS (free local LLM solution) Linux now includes Ollama (0.11.4) built-in for immediate local LLM support ARM64 support for both Linux and Windows platforms Platform & Infrastructure Expanded Linux support with automatic apparmor rules and .desktop file creation NVIDIA NIM being phased out in favor of newer solutions Upgraded core Electron version for improved stability UI/UX Improvements Model swap capability during chats (Ctrl/Cmd+Shift+L) Workspace and thread searching in sidebar System prompt version tracking and restoration Enhanced mobile support with Android beta app Developer Features MCP (Model Context Protocol) compatibility No-code AI agent builder Enhanced API endpoints and developer tools Multi-modal support for both open and closed-source LLMs Internationalization Added Portuguese and Estonian translations Improved multi-language OCR support Expanded localization coverage The update represents a massive leap from the initial version, transforming from a basic document chat system to a comprehensive AI agent platform with robust local operation capabilities and extensive customization options.

@TheMoodBoardz Does it fail with tgz format also? Not sure how to debug this since it is just crashing with no real logs. If you reach out at support@cloudron.io , we can debug further.

Glad you found this part, I've change the title to be more specific. I have never heard of Identity Enterprise Workspace actually.

Thanks @girish I will build a custom version then.

-------------------------------------------- REQUIRED: BASIC APP SETTINGS -------------------------------------------- APP_ENV=production APP_DEBUG=false APP_KEY=base64:REDACTED APP_URL=${CLOUDRON_APP_ORIGIN} APP_TIMEZONE='GMT' APP_LOCALE=en MAX_RESULTS=500 -------------------------------------------- REQUIRED: DATABASE SETTINGS -------------------------------------------- DB_CONNECTION=mysql DB_HOST=${CLOUDRON_MYSQL_HOST} DB_DATABASE=${CLOUDRON_MYSQL_DATABASE} DB_USERNAME=${CLOUDRON_MYSQL_USERNAME} DB_PASSWORD=${CLOUDRON_MYSQL_PASSWORD} DB_PREFIX=null DB_DUMP_PATH='/usr/bin' DB_CHARSET=utf8mb4 DB_COLLATION=utf8mb4_unicode_ci -------------------------------------------- OPTIONAL: SSL DATABASE SETTINGS -------------------------------------------- DB_SSL=false DB_SSL_IS_PAAS=false DB_SSL_KEY_PATH=null DB_SSL_CERT_PATH=null DB_SSL_CA_PATH=null DB_SSL_CIPHER=null -------------------------------------------- REQUIRED: OUTGOING MAIL SERVER SETTINGS -------------------------------------------- MAIL_DRIVER=smtp MAIL_HOST=${CLOUDRON_MAIL_SMTP_SERVER} MAIL_PORT=${CLOUDRON_MAIL_SMTP_PORT} MAIL_USERNAME=${CLOUDRON_MAIL_SMTP_USERNAME} MAIL_PASSWORD=${CLOUDRON_MAIL_SMTP_PASSWORD} MAIL_ENCRYPTION=null MAIL_FROM_ADDR=${CLOUDRON_MAIL_FROM} MAIL_FROM_NAME=${CLOUDRON_MAIL_FROM_DISPLAY_NAME} MAIL_REPLYTO_ADDR=${CLOUDRON_MAIL_FROM} MAIL_REPLYTO_NAME=${CLOUDRON_MAIL_FROM_DISPLAY_NAME} MAIL_BACKUP_NOTIFICATION_ADDRESS=you@example.com -------------------------------------------- REQUIRED: IMAGE LIBRARY This should be gd or imagick -------------------------------------------- IMAGE_LIB=gd -------------------------------------------- OPTIONAL: SESSION SETTINGS -------------------------------------------- SESSION_LIFETIME=90 EXPIRE_ON_CLOSE=true ENCRYPT=true COOKIE_NAME=${CLOUDRON_APP_HOSTNAME} COOKIE_DOMAIN=${CLOUDRON_APP_DOMAIN} SECURE_COOKIES=true -------------------------------------------- OPTIONAL: SECURITY HEADER SETTINGS -------------------------------------------- APP_TRUSTED_PROXIES=127.0.0.1,${CLOUDRON_PROXY_IP} ALLOW_IFRAMING=true REFERRER_POLICY=same-origin ENABLE_CSP=true CORS_ALLOWED_ORIGINS=null ENABLE_HSTS=false -------------------------------------------- OPTIONAL: CACHE SETTINGS -------------------------------------------- CACHE_DRIVER=file SESSION_DRIVER=redis QUEUE_DRIVER=sync CACHE_PREFIX=snipeit -------------------------------------------- OPTIONAL: REDIS SETTINGS -------------------------------------------- REDIS_HOST=${CLOUDRON_REDIS_HOST} REDIS_PASSWORD=${CLOUDRON_REDIS_PASSWORD} REDIS_PORT=${CLOUDRON_REDIS_PORT} -------------------------------------------- OPTIONAL: MEMCACHED SETTINGS -------------------------------------------- MEMCACHED_HOST=null MEMCACHED_PORT=null -------------------------------------------- OPTIONAL: AWS S3 SETTINGS -------------------------------------------- AWS_SECRET=null AWS_KEY=null AWS_REGION=null AWS_BUCKET=null -------------------------------------------- OPTIONAL: LOGIN THROTTLING -------------------------------------------- LOGIN_MAX_ATTEMPTS=3 LOGIN_LOCKOUT_DURATION=60 -------------------------------------------- OPTIONAL: MISC -------------------------------------------- APP_LOG=single APP_LOG_MAX_FILES=10 APP_LOCKED=false FILESYSTEM_DISK=local APP_CIPHER=AES-256-CBC #GOOGLE_MAPS_API= BACKUP_ENV=true LDAP_MEM_LIM=500M LDAP_TIME_LIM=600

@nebulon It took a while to look into it - on my external facing URL it was my proxy & firewall that was blocking it. I switch to using the local IP & changed the Base DN as you mentioned & it is now pulling in users. Thanks for your help!

@girish yes that's fixed it. Thanks

I think I have fixed it - I was not putting it in the custom config.json file. It's all working now. Thanks!