Originally created by @abdelba on GitHub (Apr 8, 2025).
To Reproduce
When trying to create from lowcoder template, the error e.config.domains.every is not a function is displayed
Current vs. Expected behavior
The error appears while we would like to create the lowcoder instance instead.
Provide environment information
Dokploy Version v0.21.4
Which area(s) are affected? (Select all that apply)
Application
Are you deploying the applications where Dokploy is installed or on a remote server?
Same server where Dokploy is installed
Additional context
No response
Will you send a PR to fix it?
No
Originally created by @abdelba on GitHub (Apr 8, 2025).
### To Reproduce
When trying to create from lowcoder template, the error `e.config.domains.every is not a function` is displayed
<img width="1384" alt="Image" src="https://github.com/user-attachments/assets/4b32a5ff-1a9f-4b32-a386-6e96e83f629e" />
### Current vs. Expected behavior
The error appears while we would like to create the lowcoder instance instead.
### Provide environment information
```bash
Dokploy Version v0.21.4
```
### Which area(s) are affected? (Select all that apply)
Application
### Are you deploying the applications where Dokploy is installed or on a remote server?
Same server where Dokploy is installed
### Additional context
_No response_
### Will you send a PR to fix it?
No
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @abdelba on GitHub (Apr 8, 2025).
To Reproduce
When trying to create from lowcoder template, the error
e.config.domains.every is not a functionis displayedCurrent vs. Expected behavior
The error appears while we would like to create the lowcoder instance instead.
Provide environment information
Which area(s) are affected? (Select all that apply)
Application
Are you deploying the applications where Dokploy is installed or on a remote server?
Same server where Dokploy is installed
Additional context
No response
Will you send a PR to fix it?
No
@Siumauricio commented on GitHub (Apr 9, 2025):
Fixed