Did they work before? Or are they new?
If they worked before - you need to check the public IP and WAN IP on your router (they should match), perhaps they got changed but your DDNS hostname is not updated, or your ISP could put you behind their NAT (CGNAT).
If you forward unique ports to the same host, make sure that the destination port matched the source port, i.e. 28967 UDP+TCP is forwarded to 28967 UDP+TCP on your host, 28968 UDP+TCP is forwarded to 28968 UDP+TCP on your host, etc.
If new - use the checklist:
Make sure that you generated an identity, not copied. Each unique identity should be signed with a new authorization token.
When you generate an identity, you can use a different name to do not mix with existing identity, for example:
identity create storagenode2
The identity will be in ~/.local/share/storj/identity/storagenode2
Then you need to sign it with a new authorization token.
identity authorize storagenode2 your@email:1Ffjgirpwpksoief...
Then you can move this new identity to the data location and use this new path in your docker run command.
When you forwarding port - make sure that it’s unique. In your docker run command you should use this port in the ADDRESS parameter and in the left part of port mapping, i.e. -p 28968:28967/tcp -p 28968:28967/udp -e ADDRESS=your.ddns.address:28968
Check that you bind the correct identity path from the host to the /app/identity path inside the container.