Samba share add-on not starting up

Configuration
1

Samba share add worked fine until a few days ago, but it doesn’t start. username and password are already set up correctly.
error

[12:58:52] ERROR: Something went wrong contacting the API
[12:58:55] FATAL: Setting a username and password is required!
s6-rc: warning: unable to start service init-smbd: command exited 1
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-smbd: starting
2

This is probably going to be hard for anyone here to diagnose because you would need to share your actual config, but since that contains your username and password it’s not only ill advised to do that but I’m sure you just simply wouldn’t want to do it.

What you might try is simplifying your username and password as much as you can, removing special characters and see if it’s a complexity issue. I don’t know why it would work one day an stop the next unless an update was applied either to HA Samba implementation or to the other computer.

The message is clearly bombing on the user/pass, something somewhere must have changed if it worked before.

3 
username: xxxxxxxxxxx
password: xxxxxxxxxxxxxxxxx
workgroup: WORKGROUP
compatibility_mode: false
veto_files:
  - ._*
  - .DS_Store
  - Thumbs.db
  - icon?
  - .Trashes
allow_hosts:
  - 10.0.0.0/8
  - 172.16.0.0/12
  - 192.168.0.0/16
  - 169.254.0.0/16
  - fe80::/10
  - fc00::/7
4

The reason I answered the way I did, and why your config post doesn’t help, is to see if how your user/pass were set up in case they were the problem.

Have you attempted to simplify them with no special characters? Something like:

username: testuser
password: password123

And set that account up on the other side and see if that is the problem. And depending on the other side, compatibility mode may need to be enabled.

5

my username is all lowercase with no spaces and my password is a mix of numbers, upper and lower case alphabet with no spaces either.
Let me try with this username and password combination.

6

And don’t forget to try the compatibility mode. What is the other end?

7

tested with this combination too same issue

[02:49:47] FATAL: Setting a username and password is required!
s6-rc: warning: unable to start service init-smbd: command exited 1
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

username: testuser
password: password123
workgroup: WORKGROUP
compatibility_mode: false
veto_files:
  - ._*
  - .DS_Store
  - Thumbs.db
  - icon?
  - .Trashes
allow_hosts:
  - 10.0.0.0/8
  - 172.16.0.0/12
  - 192.168.0.0/16
  - 169.254.0.0/16
  - fe80::/10
  - fc00::/7
8

It looks right to me. Is this HAOS?

9

yes HAOS on rpi4 . but it isn’t working.

[02:53:02] ERROR: Something went wrong contacting the API
[02:53:04] FATAL: Setting a username and password is required!
10

used this add-on to fix this issue. the official one is not working for me.