express-flash | Flash Messages for your Express Application | Runtime Evironment library

As I already mentioned in my comment, you don't have a /user route therefore you will get a 404 NotFound error.

Change this

Delete package lock file and Try using this command to rebuild the container.

To debug why you're not getting a session cookie, replace your existing session middleware with just this:

Will express-flash work with clustering?

It depends upon whether you're running clustering-compatible session middleware.

The express-flash module uses the connect-flash module which stores its flash message in req.session. So, for a future request (often a redirect) to be able to access the flash message, the user's session has to be preserved.

So, if you're using a session implementation that is compatible with clustering, then express-flash will also work with clustering. If you either don't have any session support configured or the session you're using is not clustering compatible (e.g. not based on some centralized store that all clustered processes can access), then express-flash will not work properly.

So, it depends upon whether you're running a clustering-compatible session or not.

FYI, this doesn't really have anything to do with res.locals as that's not where the flash data is stored (since that's a temporary object that exists only for the duration of one request). That's just the final place that the data is placed by the flash middleware when there's an incoming request and it's placed there so that templates can access it if they wish.

There's a syntax error when adding the user info to the users database. Instead of:

Going off the documentation, the saveUninitialized flag should be getting set to false -

Forces a session that is "uninitialized" to be saved to the store. A session is uninitialized when it is new but not modified. Choosing false is useful for implementing login sessions, reducing server storage usage, or complying with laws that require permission before setting a cookie. Choosing false will also help with race conditions where a client makes multiple parallel requests without a session. The default value is true, but using the default has been deprecated, as the default will change in the future. Please research into this setting and choose what is appropriate to your use-case.

https://github.com/expressjs/session#saveuninitialized

I’ve found how to do it.
For that you should first add CONFIG_ARCH_VEXPRESS and ran ‘make V=1 ARCH=arm64 CROSS_COMPILE=aarch64-none-elf- dtbs |& tee logx’
Dtbs for ARCH_VEXPRESS are generated in the dts directory. Then you can see the command to make the dtb (in the logx file).
Below is the command. Lots of options for the dtc(related to unit address too).

mkdir -p arch/arm64/boot/dts/arm/ ; gcc -E -Wp,-MD,arch/arm64/boot/dts/arm/.fvp-base-revc.dtb.d.pre.tmp -nostdinc -I./scripts/dtc/include-prefixes -undef -D__DTS__ -x assembler-with-cpp -o arch/arm64/boot/dts/arm/.fvp-base-revc.dtb.dts.tmp arch/arm64/boot/dts/arm/fvp-base-revc.dts ; ./scripts/dtc/dtc -O dtb -o arch/arm64/boot/dts/arm/fvp-base-revc.dtb -b 0 -iarch/arm64/boot/dts/arm/ -i./scripts/dtc/include-prefixes -Wno-unit_address_vs_reg -Wno-unit_address_format -Wno-avoid_unnecessary_addr_size -Wno-alias_paths -Wno-graph_child_address -Wno-simple_bus_reg -Wno-unique_unit_address -Wno-pci_device_reg -d arch/arm64/boot/dts/arm/.fvp-base-revc.dtb.d.dtc.tmp arch/arm64/boot/dts/arm/.fvp-base-revc.dtb.dts.tmp ; cat arch/arm64/boot/dts/arm/.fvp-base-revc.dtb.d.pre.tmp arch/arm64/boot/dts/arm/.fvp-base-revc.dtb.d.dtc.tmp > arch/arm64/boot/dts/arm/.fvp-base-revc.dtb.d

You can use this command to make a specific dtb file.

You need to initialize passport before using it, the error is fairly straightforward. If you are still getting error then kindly share your app.js as well. Anyways, just do this:

To solve this problem, I transferred this code from login.js to server.js: