William Luke

Just ran into the same issue, ``` OS: Ubuntu 22.04 LTS x86_64 Kernel: 5.15.0-33-generic Node: v16.13.2 OpenSSL: 3.0.2 15 Mar 2022 (Library: OpenSSL 3.0.2 15 Mar 2022) google-spreadsheet: 3.3.0 ```...

Setting `OPENSSL_CONF` envar to `/dev/null` works but :grimacing:

@theoephraim Any what's going on here?

Just run into the `Error: 401 Unauthorized: unauthorized access` after the 1.8 -> 2.3 upgrade ``` > ulimit -a real-time non-blocking time (microseconds, -R) unlimited core file size (blocks, -c)...

Managed to find the upgrade log ``` influxd upgrade {"level":"info","ts":1656536691.8887737,"caller":"upgrade/upgrade.go:401","msg":"Starting InfluxDB 1.x upgrade"} {"level":"info","ts":1656536691.889225,"caller":"upgrade/upgrade.go:404","msg":"Upgrading config file","file":"/etc/influxdb/influxdb.conf"} {"level":"info","ts":1656536691.8897223,"caller":"upgrade/upgrade.go:408","msg":"Config file upgraded.","1.x config":"/etc/influxdb/influxdb.conf","2.x config":"/root/.influxdbv2/config.toml"} {"level":"info","ts":1656536691.8898306,"caller":"upgrade/upgrade.go:418","msg":"Upgrade source paths","meta":"/var/lib/influxdb/meta","data":"/var/lib/influxdb/data"} {"level":"info","ts":1656536691.889981,"caller":"upgrade/upgrade.go:419","msg":"Upgrade target paths","bolt":"/root/.influxdbv2/influxd.bolt","engine":"/root/.influxdbv2/engine"} {"level":"info","ts":1656536691.8978586,"caller":"bolt/bbolt.go:83","msg":"Resources opened","service":"bolt","path":"/root/.influxdbv2/influxd.bolt"} {"level":"info","ts":1656536691.8995106,"caller":"migration/migration.go:175","msg":"Bringing...

Could someone who is experiencing this issue please post your Prisma schema and indicate whether you are using the stock `nextauthjs/next-auth` prisma adapter or the adapter from `nextauthjs/adapters`

Hey, @bhatvikrant Do you have a reproduction I can look at? From the above :point_up: errors it seems that the adapter is trying to create a new user but there...

Thanks, @bhatvikrant, I'll check it out when you are ready :)

Thanks @bhatvikrant, I'll have a dig around tomorrow morning

So there are quite a few different issues stuffed into this issue. @bhatvikrant Your issue is because the GitHub `providerAccountId` given to the adapter is a number and in the...