Forem: Rajib Ahmed

fixing Ubuntu login issues, including login loops, .Xauthority problems, and home directory permission issues.

Rajib Ahmed — Mon, 16 Feb 2026 16:19:14 +0000

fixing Ubuntu login issues, including login loops, .Xauthority problems, and home directory permission issues.

A comprehensive solution for fixing common Ubuntu login issues, including login loops, .Xauthority problems, and home directory permission issues.

🚨 Common Ubuntu Login Issues

This script addresses the following common login problems:

Login Loop - You enter your password correctly, but the screen goes black and returns to the login screen
.Xauthority Issues - Corrupted X authority files preventing GUI login
Home Directory Permission Problems - Incorrect ownership or permissions on home directory
Temporary Profile - System creating temporary profiles due to file access issues
Display Manager Problems - Issues with GDM3, LightDM, or SDDM configuration

📋 Prerequisites

Ubuntu/Debian-based Linux distribution
Root/sudo access
Access to TTY console (Ctrl+Alt+F3)

🚀 Quick Start

Direct Run From GitHub Repo

Run the script directly without downloading a local file:

curl -fsSL https://raw.githubusercontent.com/rajibdpi/ubuntu-login/main/fix.sh | sudo bash

From the Login Screen

If you're stuck at the login screen:

Press Ctrl+Alt+F3 to access a text console
Login with your username and password
Run the fix script directly from GitHub:

# Run the script (will auto-detect your username)
curl -fsSL https://raw.githubusercontent.com/rajibdpi/ubuntu-login/main/fix.sh | sudo bash

Manual Usage

If auto-detection picks the wrong user, set the target explicitly:

curl -fsSL https://raw.githubusercontent.com/rajibdpi/ubuntu-login/main/fix.sh | sudo bash -s -- --user username

Replace username with the actual username that has login issues.

Optional: Reset GNOME User Config

If login issues are caused by broken GNOME user settings/extensions, run with:

curl -fsSL https://raw.githubusercontent.com/rajibdpi/ubuntu-login/main/fix.sh | sudo bash -s -- --reset-gnome

🔧 What the Script Does

The script performs the following fixes:

1. Auto-Detects Target User

Uses SUDO_USER first
Falls back to logname
Final fallback is first regular local user (UID >= 1000)

2. Fixes `.Xauthority` and `.ICEauthority`

Backs up existing files with timestamp suffix
Removes broken authority files that can cause login loops

3. Repairs Ownership and PATH in User Shell Files

Runs ownership repair on the user home directory
Backs up .profile, .bashrc, .bash_profile, .zprofile, .zshrc
Appends a safe PATH export to .profile and .bashrc if missing

4. Repairs Core Desktop/Login Packages

Runs apt-get update
Runs apt-get -f install -y and dpkg --configure -a
Reinstalls gdm3, gnome-shell, ubuntu-session, and xorg
Enables gdm3

5. Optional GNOME Profile Reset

With --reset-gnome, backs up and resets:
- .config
- .local/share
- .cache

6. Rewrites Global PATH in `/etc/environment`

Backs up existing /etc/environment
Rewrites it to:
- PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"

⚠️ Safety Features

Creates backups of all files before modification
Validates target user and home directory before making changes
Requires root privileges for safety
Uses strict Bash mode (set -euo pipefail)

🔍 Troubleshooting

If the script doesn't resolve your issue, try these additional steps:

1. Check System Logs

journalctl -xe

2. Reconfigure Display Manager

# For GDM3
sudo dpkg-reconfigure gdm3

# For LightDM
sudo dpkg-reconfigure lightdm

3. Check for Disk Space Issues

df -h

If your disk is full, clean up space:

# Clean apt cache
sudo apt-get clean

# Remove old kernels
sudo apt-get autoremove

4. Verify Home Directory Permissions

ls -la /home/username

The home directory should be owned by the user with 755 permissions.

5. Check Authentication Logs

sudo tail -f /var/log/auth.log

6. Try Creating a New User

As a test, create a new user to see if the issue is system-wide:

sudo adduser testuser

🐛 Known Limitations

The script must be run from a TTY console or SSH session, not from the GUI
Requires sudo/root access
Reinstalling packages requires network access to apt repositories
The script rewrites /etc/environment PATH to a known-safe value

💡 Prevention Tips

To avoid login issues in the future:

Regular Backups - Keep backups of your home directory
Monitor Disk Space - Keep at least 10% free space
Careful with Permissions - Avoid using sudo with GUI applications
Update Regularly - Keep your system updated
Graceful Shutdowns - Always shutdown properly to avoid file corruption

🤝 Contributing

Contributions are welcome! Please feel free to submit issues or pull requests.

📄 License

This project is licensed under the GNU General Public License v3.0 - see the LICENSE file for details.

🙏 Acknowledgments

This script was created to help users resolve common Ubuntu login issues based on community solutions and best practices.

⚡ Emergency Recovery

If you cannot access TTY console:

Boot from Ubuntu Live USB
Mount your main partition
Chroot into your system
Run the fix script
Reboot

Example:

sudo mount /dev/sdaX /mnt
sudo mount --bind /dev /mnt/dev
sudo mount --bind /proc /mnt/proc
sudo mount --bind /sys /mnt/sys
sudo chroot /mnt
curl -fsSL https://raw.githubusercontent.com/rajibdpi/ubuntu-login/main/fix.sh | bash
exit
sudo reboot

Replace /dev/sdaX with your actual root partition.

Install and Run Let's Encrypt Certbot Every 60 Days with systemd Timer

Rajib Ahmed — Sat, 21 Jun 2025 19:00:07 +0000

Install and Run Let's Encrypt Certbot Every 60 Days with systemd Timer

If you're managing Let's Encrypt SSL certificates on a Linux server, you probably use Certbot to automate SSL issuance and renewal. By default, Certbot is configured to renew certificates every 60 days using a systemd timer (certbot.timer) or a cron job. But what if you want to install Certbot and then enforce exactly every 60 days using systemd?

This post shows you how to install Certbot and customize the certbot.timer to renew certificates every 60 days using systemd.

📦 Install Certbot

Depending on your Linux distribution, use one of the following commands:

For Debian/Ubuntu:

sudo apt update
sudo apt install certbot python3-certbot-nginx -y

For CentOS/RHEL:

sudo dnf install epel-release
sudo dnf install certbot python3-certbot-nginx -y

🔐 Obtain a Certificate (One-time setup)

Replace example.com with your actual domain:

sudo certbot --nginx -d example.com -d www.example.com

Follow the prompts to complete the certificate issuance and Nginx configuration.

🔁 Why 60 Days?

Let's Encrypt certificates are valid for 90 days, and the official recommendation is to renew at or before 60 days to avoid the risk of expiry due to failures or downtimes.

✅ Recommended: Automate renewals every 60 days for safety and peace of mind.

⚙️ Set Up systemd Timer to Run Every 60 Days

1️⃣ Open the Certbot Timer Override

sudo systemctl edit certbot.timer

2️⃣ Add the Override Configuration

Paste the following lines:

[Timer]
OnCalendar=
OnBootSec=10min
OnUnitActiveSec=5184000
Persistent=true

💡 What This Means:

OnCalendar=: Clears the default calendar schedule.
OnBootSec=10min: Waits 10 minutes after boot before the first run.
OnUnitActiveSec=5184000: Runs the timer every 60 days (60 × 24 × 60 × 60 = 5,184,000 seconds).
Persistent=true: Ensures missed events run at the next boot (if the server was off).

3️⃣ Save and Exit

If using nano, press Ctrl + O then Enter, and then Ctrl + X.

4️⃣ Apply the Changes

sudo systemctl daemon-reexec
sudo systemctl restart certbot.timer

5️⃣ Confirm It’s Working

systemctl list-timers certbot.timer

Example output:

NEXT                         LEFT       LAST                         PASSED     UNIT            ACTIVATES
Sat 2025-08-21 00:00:00 UTC  60d left   Sun 2025-06-22 00:00:00 UTC  1min ago   certbot.timer   certbot.service

🔍 Bonus: Check Certificate Expiry Date

To manually check your current certificate’s expiry date:

openssl x509 -in /etc/letsencrypt/live/YOURDOMAIN/fullchain.pem -noout -enddate

✅ Conclusion

Using systemd's powerful timers, you can fully automate Certbot to renew every 60 days — following best practices for secure and reliable SSL management.

Just be sure to monitor for errors, and consider using email or system logs to stay informed about renewal status.

FileBrowser is an excellent Web-Based File Manager

Rajib Ahmed — Mon, 02 Sep 2024 17:04:02 +0000

FileBrowser is a web-based file manager that allows users to manage files and directories on a server through a browser interface. It provides a simple and intuitive way to perform file operations like uploading, downloading, deleting, renaming, and editing files, as well as managing directories. Here’s how FileBrowser works:

1. Architecture Overview

Backend: FileBrowser is written in Go, a statically-typed, compiled language known for its simplicity and efficiency. The backend handles file operations, authentication, and communication with the frontend.
Frontend: The frontend is built with HTML, CSS, and JavaScript, providing a user-friendly interface. It communicates with the backend via HTTP/HTTPS requests, sending commands to the backend and receiving data in return.
Database: FileBrowser uses a SQLite database to store user accounts, permissions, and settings. The database file is typically named filebrowser.db.

2. Key Features

File Management: Users can browse directories, view files, upload and download files, and perform file operations like rename, move, copy, and delete.
User Management: FileBrowserallows you to create multiple user accounts with different permissions. This means you can control who has access to specific directories and what operations they can perform.
Authentication: Users can be authenticated using basic credentials (username and password). The backend manages user sessions and controls access based on the defined permissions.
Customizability: You can customize the appearance and behavior of FileBrowser by modifying the configuration, adding themes, and using custom CSS.
Security: FileBrowser supports HTTPS, which can be enabled to secure the connection between the user’s browser and the server. It also allows setting up access control to restrict users to specific directories and actions.

3. How It Works: Step-by-Step

1. Starting the Server

When you start FileBrowser, it initializes a web server (usually on port 8080).
The server loads configurations from the filebrowser.db database, including user accounts, settings, and the root directory from which users can browse files.

2. User Authentication

When a user attempts to access the FileBrowserinterface, they are prompted to log in.
The username and password are checked against the stored credentials in the database.
Upon successful authentication, a session is created, allowing the user to interact with the file system.

3. File Operations

Browsing: Users can navigate the directory structure starting from the root directory specified during FileBrowser setup.
Uploading: Files can be uploaded directly through the web interface, where they are stored on the server in the selected directory.
Downloading: Users can download files by clicking on them, which sends the file from the server to the user's device.
Editing: Text files can be edited directly within the browser, with changes being saved back to the server.
Deleting and Renaming: Files and directories can be deleted or renamed via the interface, with changes reflected immediately on the server.

4. User Interface

The frontend displays files and directories in a hierarchical view.
Users can switch between different views (e.g., list view, grid view).
The interface includes options for file searching, sorting, and filtering.

5. Customization and Theming

Admin users can customize the appearance of FileBrowser by applying themes, modifying CSS, or adding custom branding.
Configuration settings, including user permissions and directory access, can be adjusted through the admin panel.

6. Security and SSL

To secure the connection, FileBrowser can be configured to use HTTPS by providing an SSL certificate and key.
Access controls allow the admin to restrict user actions, such as preventing certain users from deleting or editing files.

4. Deployment

FileBrowser can be deployed on various platforms, including Linux, Windows, and macOS. It can run as a standalone application or as a service, and it can be integrated into existing infrastructure, such as a web server like Apache or Nginx.

Running as a Service: On Linux, FileBrowser can be run as a systemd service, ensuring it starts automatically with the system and runs in the background.
Docker: FileBrowser is also available as a Docker image, making it easy to deploy in containerized environments.

5. Usage Scenarios

Personal File Management: FileBrowser can be used by individuals to manage their files on a personal server, providing remote access to their data.
Shared Hosting: Web hosting providers can offer FileBrowser to their clients as a file management tool.
Corporate File Sharing: Organizations can use FileBrowser for secure file sharing among employees, with access controls tailored to different user roles.

Conclusion

FileBrowser is a versatile and powerful tool for managing files on a server via a web interface. It provides a simple, secure, and customizable platform for file management, making it suitable for both personal and professional use. Whether you're hosting it on a local server or in the cloud, FileBrowser simplifies file operations and offers robust features for user management and security.

FileBrowser (Service) Configuring to work with Apache2 as a reverse proxy on Ubuntu 24.04

Rajib Ahmed — Mon, 02 Sep 2024 17:00:53 +0000

FileBrowser service by configuring it to work with Apache2 as a reverse proxy on Ubuntu 24.04. Here’s how you can set it up:

Step 1: Install Apache2
First, ensure that Apache2 is installed and running on your system:

bash sudo apt update sudo apt install apache2 sudo systemctl start apache2 sudo systemctl enable apache2
Step 2: Install and Configure FileBrowser
Download and set up FileBrowser:

Download FileBrowser:

bash curl -fsSL https://filebrowser.org/cli.sh | bash
Run FileBrowser:
bash filebrowser -r /path/to/your/files
Access FileBrowser: You should now be able to access FileBrowser locally at http://127.0.0.1:8080.

Step 3: Configure Apache2 as a Reverse Proxy
To make FileBrowser accessible through Apache2, configure Apache2 as a reverse proxy:

Enable the necessary Apache2 modules:

sudo a2enmod proxy
sudo a2enmod proxy_http
sudo systemctl restart apache2

Create a new virtual host file for FileBrowser:

bash sudo nano /etc/apache2/sites-available/filebrowser.conf
Add the following configuration:

`apache

ServerAdmin webmaster@localhost
DocumentRoot /var/www/html

ProxyPreserveHost On
ProxyPass / http://127.0.0.1:8080/
ProxyPassReverse / http://127.0.0.1:8080/

ErrorLog ${APACHE_LOG_DIR}/filebrowser_error.log
CustomLog ${APACHE_LOG_DIR}/filebrowser_access.log combined

`
Enable the new virtual host:

bash sudo a2ensite filebrowser.conf sudo systemctl reload apache2
Step 4: Access FileBrowser via Apache2
You should now be able to access FileBrowser via your domain or IP through Apache2.

If you want to run FileBrowser as a system service, you can create a service file:

Create a service file:
bash sudo nano /etc/systemd/system/filebrowser.service
Add the following content:

`ini
[Unit]
Description=File Browser
After=network.target

[Service]
User=www-data
ExecStart=/usr/local/bin/filebrowser -r /path/to/your/files
Restart=on-failure

[Install]
WantedBy=multi-user.target`

Enable and start the service:
bash sudo systemctl enable filebrowser sudo systemctl start filebrowser

This setup will ensure that FileBrowser is running and accessible through Apache2 on your Ubuntu 24.04 system.

FileBrowser Installation Steps from Source Code on Ubuntu 24.04

Rajib Ahmed — Sun, 01 Sep 2024 13:12:53 +0000

FileBrowser from source on Ubuntu 24.04, follow these steps:

1. Prerequisites

Ensure you have the necessary tools and dependencies installed:

sudo apt update
sudo apt install -y build-essential git

2. Clone the FileBrowser Repository

FileBrowser's source code is hosted on GitHub. Clone the repository using git:

git clone https://github.com/filebrowser/filebrowser.git
cd filebrowser/frontend && npm install && npm run build && cd ..

3. Build FileBrowser

FileBrowser is written in Go. You'll need Go installed to build it.

Install Go

If Go is not already installed, you can install it using the following commands:

sudo apt install -y golang

Verify the installation:

go version

Build FileBrowser

Navigate to the FileBrowser directory and build the application:

go build -o filebrowser

This will create an executable file named filebrowser in the current directory.

4. Move the Executable

Move the filebrowser binary to a directory in your PATH, like /usr/local/bin, so it can be easily executed:

sudo mv filebrowser /usr/local/bin/

5. Create a Systemd Service File

To manage FileBrowser as a systemd service, create a service file:

sudo nano /etc/systemd/system/filebrowser.service

Add the following content to the service file:

Description=File Browser
After=network.target

[Service]
User=yourusername
Group=yourusername
ExecStart=/usr/local/bin/filebrowser -r /path/to/your/root/directory
Restart=on-failure

[Install]
WantedBy=multi-user.target

Replace yourusername with your actual username and adjust the ExecStart path if necessary.

6. Reload Systemd and Start the Service

Reload systemd to apply the new service configuration:

sudo systemctl daemon-reload

Start the FileBrowser service:

sudo systemctl start filebrowser

Enable the service to start on boot:

sudo systemctl enable filebrowser

7. Configure FileBrowser

If needed, create a configuration file for FileBrowser or modify its default settings.

Configuration File

You can specify additional configurations using command-line options or by creating a configuration file. Check the FileBrowser documentation for detailed configuration options.

8. Verify the Installation

Check the status of the FileBrowser service to ensure it's running:

bash

Copy code

sudo systemctl status filebrowser

You should see the service status as active (running).

9. Access FileBrowser

Open your web browser and navigate to http://localhost:8080 (or the port you configured) to access the FileBrowser web interface.

Conclusion

By following these steps, you should be able to install FileBrowser from source on Ubuntu 24.04 and set it up to run as a systemd service. If you encounter any issues, refer to the FileBrowser documentation or check the service logs for more details.

How to make automatically start the WSL services for ssh, apache2, mysql at Windows Startup

Rajib Ahmed — Fri, 24 Nov 2023 10:30:40 +0000

How to make automatically run the WSL services for ssh, apache2, mysql at Startup:

*Step: 1 *

Add below lines in

sudo nano /etc/sudoers

WSL to prevent asking password:
%sudo ALL=(ALL) NOPASSWD: /usr/sbin/service ssh start %sudo ALL=(ALL) NOPASSWD: /usr/sbin/service apache2 start %sudo ALL=(ALL) NOPASSWD: /usr/sbin/service mysql start
*Step: 2 *

Create wslservices.bat file in Windows startup directory:

Press Win + R and type shell:startup
*Step: 3 *

Add these lines in wslservices.bat and save it.
wsl sudo service ssh start wsl sudo service apache2 start wsl sudo service mysql start
After restarting the host computer of WSL, services it will be start automatically.

Forem: Rajib Ahmed

fixing Ubuntu login issues, including login loops, .Xauthority problems, and home directory permission issues.

fixing Ubuntu login issues, including login loops, .Xauthority problems, and home directory permission issues.

🚨 Common Ubuntu Login Issues

📋 Prerequisites

🚀 Quick Start

Direct Run From GitHub Repo

From the Login Screen

Manual Usage

Optional: Reset GNOME User Config

🔧 What the Script Does

1. Auto-Detects Target User

2. Fixes .Xauthority and .ICEauthority

3. Repairs Ownership and PATH in User Shell Files

4. Repairs Core Desktop/Login Packages

5. Optional GNOME Profile Reset

6. Rewrites Global PATH in /etc/environment

⚠️ Safety Features

🔍 Troubleshooting

1. Check System Logs

2. Reconfigure Display Manager

3. Check for Disk Space Issues

4. Verify Home Directory Permissions

5. Check Authentication Logs

6. Try Creating a New User

🐛 Known Limitations

💡 Prevention Tips

🤝 Contributing

📄 License

🙏 Acknowledgments

⚡ Emergency Recovery

Install and Run Let's Encrypt Certbot Every 60 Days with systemd Timer

Install and Run Let's Encrypt Certbot Every 60 Days with systemd Timer

📦 Install Certbot

For Debian/Ubuntu:

For CentOS/RHEL:

🔐 Obtain a Certificate (One-time setup)

🔁 Why 60 Days?

⚙️ Set Up systemd Timer to Run Every 60 Days

1️⃣ Open the Certbot Timer Override

2️⃣ Add the Override Configuration

💡 What This Means:

3️⃣ Save and Exit

4️⃣ Apply the Changes

5️⃣ Confirm It’s Working

🔍 Bonus: Check Certificate Expiry Date

✅ Conclusion

FileBrowser is an excellent Web-Based File Manager

1. Architecture Overview

2. Key Features

3. How It Works: Step-by-Step

1. Starting the Server

2. User Authentication

3. File Operations

4. User Interface

5. Customization and Theming

6. Security and SSL

4. Deployment

5. Usage Scenarios

Conclusion

FileBrowser (Service) Configuring to work with Apache2 as a reverse proxy on Ubuntu 24.04

FileBrowser Installation Steps from Source Code on Ubuntu 24.04

1. Prerequisites

2. Clone the FileBrowser Repository

3. Build FileBrowser

Install Go

Build FileBrowser

4. Move the Executable

5. Create a Systemd Service File

6. Reload Systemd and Start the Service

7. Configure FileBrowser

Configuration File

8. Verify the Installation

9. Access FileBrowser

Conclusion

How to make automatically start the WSL services for ssh, apache2, mysql at Windows Startup

How to make automatically run the WSL services for ssh, apache2, mysql at Startup:

2. Fixes `.Xauthority` and `.ICEauthority`

6. Rewrites Global PATH in `/etc/environment`