Has anyone gotten the manual installation to work?

[jpbotha11]

There seems to be some "obvious" pre-setup confuration missing from the documentation, specifically:

• the setup of the postres database,
• database user and access setup
• node package conflicts (what version of node to use etc.)

Anybody else experiencing the same issues?

For reference, trying to install on Proxmox LXC using Ubuntu 22.04 template.

[MODSetter]

@jpbotha11

These are valid points I will update documentation soon to add more info for these.

[jpbotha11]

Wonderfull thank you.

[NickRahn]

I was able to get it to work. seems there may still be some req installs that are just expected to be there.

node.js
python
npm

additionally, once I was able to get it running the local login only worked for the machine it ran on i could not login from a machine on the LAN. Moving to google auth seems the same I also get "Failed to fetch"

Also seems like after you migrate to google you may not be able to use the same google email if you registered using local login. I manually went into the user table and cleared my created user. still unable to login from lan though.

[sammcj]

Can't seem to figure out the default local login details when the auth provider is set to local.

Is there a default email / password that should be used?

I tried the [email protected] / surfsense login but that complains about requiring an internet connection for the login:

[sammcj]

I'll have a hunt through the logs when I try that and bump up the log level if needed.

[MODSetter]

@jpbotha11 what val you setup for

SurfSense/surfsense_web/.env.example

Line 1 in b3d8279

NEXT_PUBLIC_FASTAPI_BACKEND_URL=http://localhost:8000

?

[sammcj]

NEXT_PUBLIC_FASTAPI_BACKEND_URL=http://surfsense_backend:8000

The backend container is named surfsense_backend which the frontend has direct access to.

[MODSetter]

@jpbotha11 try http://localhost:8000 and lmk

[sammcj]

Thanks, no that didn't fix it, I did spot this in the logs though:

 ⚠ Cross origin request detected from surfsense.my.domain to /_next/* resource. In a future major version of Next.js, you will need to explicitly configure "allowedDevOrigins" in next.config to allow this.
Read more: https://nextjs.org/docs/app/api-reference/config/next-config-js/allowedDevOrigins
 ✓ Compiled /_not-found/page in 422ms

[projx]

I've got the exact same issue... another post suggested going to /register/ but that just redirects me back to /login. I've looked in the DB, the users table seems empty.