Feature Requests

Currently I have 2 servers and I'd like to use both resources on a single endpoint instead of having to create multiple subdomains on my domain.

The current save system is good, but I have an idea to make it even more complete Imagine a .tar.gz file that contains easypanel settings parameters traefik configuration files Easypanel projects which are selected to be backup the services associated with its projects persistent volumes The main idea is that let's imagine we totally lose the data of our easypanel server, to be able to quickly restore the parameters, projects and services with their volumes in a few clicks What do you think ?

I needed a SMTP server for my host, but I couldn't use it in EasyPanel. There is some alternatives docker-based like mailcow-dockerized, docker-mailserver, mailu... But I couldn't configure it using Schema.

Chatwoot is not sending emails to create agent accounts. There seems to be an error, but I can’t find it.

I think the ability to export snapshots via API will contribute a lot to backups because we will be capable of setting a cron job to do that and export to s3.

I would like to request an upgrade to Dify v0.15.3, as the latest version provides additional API support, including DeepSeek R1 and Gemini 2.0. This upgrade is particularly significant for us, given the current industry trends and technological advancements. We kindly ask if you could consider upgrading to this latest version at your earliest convenience. Please let us know if you require any further details regarding this request.

I would like to backup my data on the same server as well as an off-site location (also S3). Would be great if I could specify multiple backup locations for a database.

Error discussed on discord forum. https://discord.com/channels/949251825511575562/1404434435436183693 My previous token expired, and now creating a new one for EasyPanel, I am getting "Github token is not valid" when trying to save it. I followed the requirements from the docs: https://easypanel.io/docs/code-sources/github . Tried both classic and fine tuned tokens, same result. Log shows: GET /user/repos - 500 with id UNKNOWN in 6ms Error in tRPC handler on path 'settings.setGithubToken': Error: Github token is not valid at dw (/app/backend.js:686:82212) ... 8 lines matching cause stack trace ... at async /app/backend.js:558:10572 { cause: Error: Github token is not valid at dw (/app/backend.js:686:82212) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async /app/backend.js:691:70440 at async Q7.Yd.middlewares (/app/backend.js:562:12637) at async _De (/app/backend.js:565:70) at async _De (/app/backend.js:565:70) at async _De (/app/backend.js:565:70) at async _De (/app/backend.js:565:70) at async t (/app/backend.js:565:407) at async /app/backend.js:558:10572, code: 'INTERNAL_SERVER_ERROR', name: 'TRPCError' }

PROBLEM EasyPanel 2.17.0+ switched from syslog to json-file logging drivers without configuration options. This breaking change forces us to stay on 2.16.0 indefinitely. Critical Issue : Even if you manually change the Docker log driver, EasyPanel resets it back to json-file on every service restart or deploy, making workarounds impossible. Customer Impact : Request Network (2x Hobby Plans, $29.80/month) - Production blocker preventing platform upgrades. WHY THIS MATTERS Technical Issue Our monitoring relies on service names in log entries for 17 critical GCP alert policies: syslog format (what we need) - includes service name: Aug 20 10:30:45 prod request-api[container]: Error message json-file format (current) - only ephemeral container ID: {"log":"Error message","stream":"stderr","time":"2025-08-20T10:30:45.123Z"} Container IDs change on restart, breaking persistent monitoring queries. EasyPanel's Rationale We understand the motivation (2.17.0 changelog) about limiting log file size - we've had disk space issues too. However, this wasn't highlighted as a breaking change affecting monitoring infrastructure. PROPOSED SOLUTION Add "Log Driver" dropdown in service configuration: • syslog (external log aggregation) • json-file (current default) • gcplogs (direct GCP integration) • fluentd (flexible log routing and processing) • none (disable logging) COMPETITIVE CONTEXT Coolify already provides this via "drain logs": https://coolify.io/docs/knowledge-base/drain-logs USE CASES External monitoring (our case) - service names for alert filtering Cloud-native - direct GCP/AWS integration Development - minimal overhead with none Compliance - integration with audit systems BUSINESS IMPACT • Risk : Evaluating migration to platforms supporting our logging needs • Opportunity : Essential for businesses with existing monitoring infrastructure IMPLEMENTATION SUGGESTION MVP : Basic dropdown with syslog , json-file , none Enhanced : Additional drivers ( gcplogs , awslogs ) + driver options --- Contact : Discord @MantisClone | Email: david.huntmateo@request.network This represents a critical need for logging flexibility that would benefit many EasyPanel customers beyond our specific use case.