Miloš Lapiš
Not able to log in. No metadata for User was found.
This is good news, and many thanks to @charles for his personal approach to solving the problem of getting Twenty CRM up and running on the PaaS cloud platform https://zerops.io. As usual, the devil is in the details. In our case, the Twenty server was starting from a bad working directory, which affected some relations to the TypeORM library, specifically to the
user.entity.js file. Everything else was fine.62 replies
Not able to log in. No metadata for User was found.
@charles I am here, just focusing on another project now. I need to switch regularly to cover all that is necessary. Time is limited, and we need to live with it. What about tomorrow? Do you know what time would be good for you?
62 replies
Not able to log in. No metadata for User was found.
I guess adding some
console.log in appropriate places would help to confirm if the expected in/out function parameters seem to be what is expected. This would probably be on a separate branch I would use as a repo source.62 replies
Not able to log in. No metadata for User was found.
In the meantime, by installing both of them, I eliminated the potential effect of missing PG extensions wrappers and mysql_fdw. However, they don't affect the problem.
PS: The wrappers extension on Ubuntu 22.04 also has a problem because the latest wrappers v0.4.1 is still using the old OpenSSL (libssl.so.1.1), which is not included on Ubuntu 22.04 and it creates also a potential security problem. ❗
62 replies
Not able to log in. No metadata for User was found.
@charles Thanks a lot for any help. It sounds like something that could have the potential to break things. 🥲 I will wait and try. And, of course, I will post the actual result. We will see ...
62 replies
Not able to log in. No metadata for User was found.
@Weiko @Jérémy I would appreciate it if you could look at the problem I described above for a few minutes. It looks like it's something trivial, but even though I made all possible tries, I could not find the right place. All seem to work correctly (making builds for BE or FE and running them, working PG db and its initial design setting, seeding with sample data, ...). But when the client tries to log in, the error
"code": "INTERNAL_SERVER_ERROR", "response": "No metadata for \"User\" was found." appears. It looks like it's related to the TypeORM library, but I can't imagine how it could be possible that my build script could be a reason for such a problem. It is simply an equivalent of the original Docker script. Thank you very much for your help.62 replies
TTwenty
•Created by Lakshan on 8/27/2024 in #💻︱development
Thread
@lakshan It sounds close to my problem. https://discord.com/channels/1130383047699738754/1277012330848321719 What exactly are you doing? Can you describe it in more detail?
1 replies
Not able to log in. No metadata for User was found.
@Brendan Thanks for the tips. I appreciate it. The manual build is a close copy of the Docker script, with minimum space to do something wrong. The
checkUserExists function is straightforward, and it's hard to imagine that the build, without any errors, can break such things. I also checked some similar or equal errors with TypeORM in other OSS projects, and most of them were related to how TypeORM and entities are implemented and called.62 replies
Not able to log in. No metadata for User was found.
@Brendan First, I apologize for the personal address. I am relatively new in the Twenty community and don't know Twenty's team yet, so I am a bit lost on who focuses on what area. I tried really hard to solve my problem but without success. It seems that it is somehow related to the TypeORM library, and somebody is certainly focusing on that area. I would like to ask if you can help connect me to him/her.
62 replies