Keep getting 404: Resource not found

[Social-Brothers]

Hi there!
I am trying to set up 2Fauth on my Digitalocean droplet. For this I installed PHP (8.1.2, with necessary extensions), Mysql and Apache.

I've followed the setup tutorial completely twice now, but still run into the same problem. When I have installed everything I get a dark 404 screen on the site with the text "404" and "Resource not found".

My virtual host looks like this:

<VirtualHost *:80>
    ServerName XXX.XXX.XXX.XXX
    ServerAdmin [email protected]
    DocumentRoot /var/www/2fauth/public

    <Directory "/var/www/2fauth/public">
        Options Indexes MultiViews
        AllowOverride None
        Require all granted
    </Directory>

    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined
</VirtualHost>

I've already tried adding or removing qoutes in the back of the and setting the AllowOverride to all, but this doesn't help my problem.

The code has not been modified directly from Github. The Artisan commands ran without any problems and my .env looks like this:

# You can change the name of the app

APP_NAME=2FAuth


# You can leave this on "local". If you change it to production most console comm>
# Never set it to "testing".

APP_ENV=local


# Set to true if you want to see debug information in error screens.

APP_DEBUG=false


# This should be your email address

[email protected]


# The encryption key for your database and sessions. Keep this very secure.
# If you generate a new one all existing data must be considered LOST.
# Change it to a string of exactly 32 chars or use command `php artisan key:gener>

APP_KEY=SomeRandomStringOf32CharsExactly


# This variable must match your installation's external address but keep in mind >
# it's only used on the command line as a fallback value.

APP_URL=http://XXX.XXX.XXX.XXX


# Turn this to true if you want your app to react like a demo.
# The Demo mode reset the app content every hours and set a generic demo user.

IS_DEMO_APP=false


# The log channel defines where your log entries go to.
# 'daily' is the default logging mode giving you 7 daily rotated log files in /st>
# Several other options exist. You can use 'single' for one big fat error log (no>
# Also available are 'syslog', 'errorlog' and 'stdout' which will log to the syst>

LOG_CHANNEL=daily


# Log level. You can set this from least severe to most severe:
# debug, info, notice, warning, error, critical, alert, emergency
# If you set it to debug your logs will grow large, and fast. If you set it to em>
# nothing will get logged, ever.

LOG_LEVEL=notice


# If you're looking for performance improvements, you could install memcached.

CACHE_DRIVER=file
SESSION_DRIVER=file
FILESYSTEM_DRIVER=local


#### Database config & credentials ####

# DB_CONNECTION=sqlite
# DB_DATABASE="path/to/your/database.sqlite"

# or if you want to use SQL (uncomment lines)

# DB_CONNECTION=mysql
# DB_HOST=127.0.0.1
# DB_PORT=3306
# DB_DATABASE=homestead
# DB_USERNAME=homestead
# DB_PASSWORD=secret
DB_CONNECTION=mysql
DB_HOST=127.0.0.1
DB_PORT=3306
DB_DATABASE=2fauth
DB_USERNAME=XXXXX
DB_PASSWORD=XXXXX

#### Mail settings ####

# Refer your email provider documentation to configure your mail settings
# Set a value for every available setting to avoid issue

MAIL_DRIVER=log
MAIL_HOST=smtp.mailtrap.io
MAIL_PORT=2525
[email protected]
MAIL_USERNAME=null
MAIL_PASSWORD=null
MAIL_ENCRYPTION=null
MAIL_FROM_NAME=null
MAIL_FROM_ADDRESS=null


#### Authentication settings ####

# The default authentication guard
#
# Supported:
#   'web-guard' : The Laravel built-in auth system (default if nulled)
#   'reverse-proxy-guard' : When 2FAuth is deployed behind a reverse-proxy that h>
#
# WARNING
# When using 'reverse-proxy-guard' 2FAuth only look for the dedicated headers and>
# authentication checks. That means your proxy is fully responsible of the authen>
# trust him as long as headers are presents.

AUTHENTICATION_GUARD=web-guard

# Name of the HTTP headers sent by the reverse proxy that identifies the authenti>
# Check your proxy documentation to find out how these headers are named (i.e 'RE>
# (only relevant when AUTHENTICATION_GUARD is set to 'reverse-proxy-guard')

AUTH_PROXY_HEADER_FOR_USER=null
AUTH_PROXY_HEADER_FOR_EMAIL=null

# Custom logout URL to open when using an auth proxy.

PROXY_LOGOUT_URL=null

#### WebAuthn settings ####

# Relying Party name, aka the name of the application.
# If blank, defaults to APP_NAME. Do not set to null.

WEBAUTHN_NAME=2FAuth

# Relying Party ID. If null, the device will fill it internally.
# See https://webauthn-doc.spomky-labs.com/pre-requisites/the-relying-party#how-t>

WEBAUTHN_ID=null

# Optional image data in BASE64 (128 bytes maximum) or an image url
# See https://webauthn-doc.spomky-labs.com/pre-requisites/the-relying-party#relyi>

WEBAUTHN_ICON=null

# Use this setting to control how user verification behave during the
# WebAuthn authentication flow.
#
# Most authenticators and smartphones will ask the user to actively verify
# themselves for log in. For example, through a touch plus pin code,
# password entry, or biometric recognition (e.g., presenting a fingerprint).
# The intent is to distinguish one user from any other.
#
# Supported:
#   'required': Will ALWAYS ask for user verification
#   'preferred' (default) : Will ask for user verification IF POSSIBLE
#   'discouraged' : Will NOT ask for user verification (for example, to minimize >

WEBAUTHN_USER_VERIFICATION=preferred

# Use this setting to declare trusted proxied.
# Supported:
#   '*': to trust any proxy
#   A comma separated IP list: The list of proxies IP to trust

TRUSTED_PROXIES=null

# Leave the following configuration vars as is.
# Unless you like to tinker and know what you're doing.

BROADCAST_DRIVER=log
QUEUE_DRIVER=sync
SESSION_LIFETIME=120

REDIS_HOST=127.0.0.1
REDIS_PASSWORD=null
REDIS_PORT=6379

PUSHER_APP_ID=
PUSHER_APP_KEY=
PUSHER_APP_SECRET=
PUSHER_APP_CLUSTER=mt1

MIX_PUSHER_APP_KEY="${PUSHER_APP_KEY}"
MIX_PUSHER_APP_CLUSTER="${PUSHER_APP_CLUSTER}"

MIX_ENV=local

Does anyone know what the problem could be?

[Social-Brothers]

This is my output in the developer tools network section:

[Bubka]

Hi,

This is most likely a permission or an apache2 mod_rewrite issue. Have a look here #34 (comment)