Samba Manager Troubleshooting Guide

Common Issues and Solutions

Check if Samba is installed and running:

sudo systemctl status smbd
sudo systemctl status nmbd

If not running, start the services:

sudo systemctl start smbd
sudo systemctl start nmbd

Check if your firewall is blocking Samba:
```
sudo ufw status
```
If the firewall is active, allow Samba traffic:
```
sudo ufw allow samba
```
Verify Samba user exists:
```
sudo pdbedit -L
```
If your user is not listed, add it:
```
sudo smbpasswd -a yourusername
```
Check share permissions:
```
ls -la /path/to/share
```
Make sure the directory has appropriate permissions (e.g., 770) and is owned by the correct user/group.
Test Samba configuration:
```
testparm
```
This will check your smb.conf for errors.

Restart Samba after configuration changes:

sudo systemctl restart smbd
sudo systemctl restart nmbd

Check network connectivity: Make sure your computer can connect to the Samba server:
```
ping hostname-or-ip
```

Terminal not appearing when clicked:
- Check if GoTTY is installed and running:
```
ps aux | grep gotty
```
- If not running, start it manually:
```
./start_terminal_service.sh
```
- Verify port 8080 is available:
```
sudo netstat -tuln | grep 8080
```

GoTTY installation issues:

If Go is not installed:

sudo apt update
sudo apt install -y golang-go

Install GoTTY manually:

go install github.com/sorenisanerd/gotty@latest
export PATH=$PATH:$(go env GOPATH)/bin

Terminal size issues:
- Check GoTTY configuration:
```
cat ~/.gotty/config.toml
```
- Make sure width and height are set to 0 for dynamic sizing:
```
width = 0
height = 0
```
Terminal access permissions:
- Make sure the user running GoTTY has appropriate permissions
- For sudo access in the terminal, make sure the user has sudo privileges
Browser issues:
- Try a different browser (Chrome or Firefox recommended)
- Clear browser cache and cookies
- Check browser console for JavaScript errors

Check if the Samba user has the correct password: Reset the Samba password:
```
sudo smbpasswd -a yourusername
```
Verify user is in the correct group:
```
groups yourusername
```
Add user to the smbusers group if needed:
```
sudo usermod -aG smbusers yourusername
```
Check share configuration: Make sure the valid users parameter includes your username or group.

Fix directory permissions:

sudo chown -R yourusername:smbusers /path/to/share
sudo chmod -R 770 /path/to/share

Check SELinux (if applicable):
```
sudo sestatus
```
If SELinux is enforcing, set the correct context:
```
sudo chcon -R -t samba_share_t /path/to/share
```

Shares not visible in Network:
- Make sure Network Discovery is turned on
- Check if the Windows Firewall is blocking access
- Try accessing the share directly using the UNC path: \\server-ip\sharename
Cannot connect to shares:
- Make sure the Windows user has the same username/password as the Samba user
- Try connecting with explicit credentials: net use Z: \\server-ip\sharename /user:username password
Reset Windows SMB cache:
```
net use * /delete
```

If you're still having issues, run the setup script as root:

sudo ./setup_samba.sh

This script will:

You can manually verify your Samba configuration:

Check /etc/samba/smb.conf for proper global settings
Check /etc/samba/shares.conf for proper share definitions
Verify that the include = /etc/samba/shares.conf line exists in the global section of smb.conf

If you're still having issues, check the Samba logs:

sudo tail -f /var/log/samba/log.smbd

You can also get more detailed logs by increasing the log level in the global section of smb.conf:

log level = 3