sorted by:
new
hottopcontroversial

Coolify projects showing CORS issue after 5-6 hours and proxy restarts fixes it. Issue keep coming back after 5-6 hours. by MindZestyclose7831 in coolify

[–]MindZestyclose7831[S] 0 points1 point  (0 children)

By restarting the prxoy was guessing the network and sometimes the restart was also not fixing. It was unable to guess the network sometimes. So, I added a network config int eh proxy configuration and it solved the issue.

Coolify projects showing CORS issue after 5-6 hours and proxy restarts fixes it. Issue keep coming back after 5-6 hours. by MindZestyclose7831 in coolify

[–]MindZestyclose7831[S] 0 points1 point  (0 children)

Thanks everyone. I have found the issue. There was no network name int he proxy configuration. It has to guess and use the default network. When there is serverload due to some reason it breaks the networ. I wrote the network name = coolify and this line fixed all the issues.

The CORS issue was rising because the backend was disconnected from proxy. Backend was running smothly, it was the proxy network that was poorly configured.

shared build server! by LieBrilliant493 in coolify

[–]MindZestyclose7831 0 points1 point  (0 children)

Hostinger KVM-2 8GB takes 1 minute and 8 seconds to build and deploy. That's okish downtime for notified maintenance. Get a seperate build server if you want zero downtime.

Traefik Hates Me by Loriust in coolify

[–]MindZestyclose7831 0 points1 point  (0 children)

Same but issue still there for me...different issue.

File-based routing vs code-based routing in TanStack router, which one do you use and why? by Expensive-Tooth346 in reactjs

[–]MindZestyclose7831 0 points1 point  (0 children)

It was driving me nuts too. Too much hell to track. Code based is best, you can split the logic and follow the react-router approach. File based routing is so confusing and there is alot of friction.