LLaVA-NeXT
LLaVA-NeXT copied to clipboard
LLaVA-VL
Finetuning Scripts
Thanks for your work on this! When will fine-tuning scripts be made available?
I encounter a similar one leading to https://letsencrypt.org/docs/too-many-registrations-for-this-ip/ which means the other server is blocked. Will see how it looks like in ~3hrs but suspect the problem to reoccur.
Version
v4.0.0-beta.306
I noticed this as well - Guessing it's due to the instance name persisting to other server's dynamic proxy configs.
This can be observed by going to Servers > Other-server > Proxy > Dynamic Configurations > File: coolify.yaml (contains certresolver for coolify's instance's set domain)
Version
v4.0.0-beta.306
I noticed this as well - Guessing it's due to the instance name persisting to other server's dynamic proxy configs.
This can be observed by going to Servers > Other-server > Proxy > Dynamic Configurations > File: coolify.yaml (contains certresolver for coolify's instance's set domain)
Version
v4.0.0-beta.306
Exactly, and even if you modify or comment out all lines in this file, everything will be reactivated upon a proxy restart (the coolify.yml file gets rewritten).
Same observation here. Second server is unable to obtain certificate (takes domain from main server). The second server should take the domain from the "Wildcard Domain" field.
Has a solution been found for this issue? I'm attempting to deploy a second server using the same public IP address. I've opened port 22 so that the main server can access the second one, but I'm unable to get it working. I expected the second server to adopt the configuration from the first one, but it seems this is not the case, as it has its own proxy settings.
Made a simple addition to /app/Models/Server.php to ignore creating coolify.yaml if the server isn't the local instance. Fixed the issue on my development build.
PR #2760
Have been facing the same issue as well, trying to connect my Raspberry Pi with coolify running on the cloud, but it keeps on picking the same domain name which I defined on coolify instance, and refresh overrides every time in raspberrypi. Ideally, there has to be an option for domain name
Is there any workaround for this?
Have been facing the same issue as well, trying to connect my Raspberry Pi with coolify running on the cloud, but it keeps on picking the same domain name which I defined on coolify instance, and refresh overrides every time in raspberrypi. Ideally, there has to be an option for domain name
Is there any workaround for this?
A current workaround is to remove the instance domain from Coolify settings, then restart the remote server's proxy. You can set the domain back in settings after the remote proxy is up.
Hopefully #2760 can be looked at soon, it seemed to resolve it for me.