Jump to content

serch826

Members
  • Posts

    25
  • Joined

  • Last visited

Posts posted by serch826

  1. So, I managed to solve the problem with SMB shares at Unraid 6.12, it was WIREGUARD that stood in the way, I had to disable the wireguard plugin in settings for VPN manager and then installed WIREGUARD-EASY from APPS in Unraid, it was just to configure wireguard docker and then added clients for vpn, it worked perfectly and SMB also works all the time, want to thank everyone who helped.

    • Like 1
  2. 14 minutes ago, serch826 said:

    No problem, you did your best, thanks for your time, i can stay at the ver. 6.11.5, as then works awesome, thanks again.

    Hi, again i managed it to work, but for this i configured Wireguard to not autostart, very stanger, i've to continius to work on this as you said the network has little problem in my settings for ver. 6.12

    Yes it works

  3. 11 minutes ago, dlandon said:

    So it shows 192.168.50.200/24 in the network setup?

     

    Do this command when SMB is working and see if the 'interfaces' command has the /24 added to 192.168.50.200:

    testparm -s

    it will be near the top.

    In the setup my interface is 192.168.50.200:24

    In testparm -s not there are just those tree interfaces but no /24

    network.jpg

  4. 3 minutes ago, dlandon said:

    That's good information, thanks.  I tried to reproduce your issue and I couldn't.

     

    Unraid 6.12 sets up some networking for Samba to be sure it is only listening on the appropriate interfaces - the 'interfaces' command.  I don't know how you have your networking setup, but those 'interfaces' are the IP addresses that Samba is listening on.  What are you doing with the Wireguard interface?  The 127.0.0.1 is the localhost or 'lo'.

     

    What I don't understand is why you had to restart Samba to get SMB shares to be visible.

     

    I see one thing I'd like you to check.  Take a look at your networking setup and confirm this setting:

    Screenshot 2023-06-16 133007.png

     

    I'm suspicious because the 'interfaces' in my test system shows:

    interfaces = 192.168.1.4/24 127.0.0.1

    notice the /24?  You're missing the mask.  This really shouldn't have anything to do with needing to restart Samba, but I'm a little suspicious the 'interfaces' is not getting set properly in a certain case keeping SMB shares from being visible, and a Samba restart fixes it.

    Hi and thanks, the Wireguard is my VPN services for accessing the LAN outside the home, i use the a lot, The /24 is automatical configured by Unraid

  5. 1 hour ago, serch826 said:

    Yes, you're right i'll look at that and will back, thanks a lot

    If i run the samba restart command it works fine

     

    1 hour ago, serch826 said:
    interfaces = 192.168.50.200 10.253.0.1 127.0.0.1

    The interface:  10.253.0.1 is from Wireguard i think, how to fix that with the interfaces? Thanks again.

  6. 37 minutes ago, dlandon said:

    I believe you might have an interface issue.  These are the interfaces in your 'testparm' output:

    interfaces = 192.168.50.200 10.253.0.1 127.0.0.1

     

    Check that these look right.  The 192.168.50.200 is your server.  The issue might be the application of the interfaces/networking is not taking on first boot.  The are networking changes new to 6.12.

     

    When this happens go to a command line and do this command:

    /etc/rc.d/rc.samba restart

    and see if SMB will work.

    Yes, you're right i'll look at that and will back, thanks a lot

  7. 18 minutes ago, JorgeB said:

    I have no other ideas other then trying a stock Unraid install and restoring only the bare minimum, like the key, super.dat and pools folder for the assignments, then re-test.

    Thanks, i also think to do that, but i will try a little more to see if i get some fix, thanks again

  8. 3 minutes ago, JorgeB said:

    To confirm if SMB was working before array re-start:

    So it's just after first array start that it stops working? That's very strange, do you have any user scripts running at first array start?

    Hi, okay i understand, no i don't have any script at först array star, with the ver.6.11.5 worked awesome

  9. 2 hours ago, JorgeB said:

    Try rebooting in safe mode, also comment or remove the line you have on SMB extras.

    Thanks for your advice, i did that, but still the issue, don't know what to do, attached the new diagnostics, thanks again.

    Edit: When in safemode it works after i started the Array so all my shares are OK, before the Array is started works also but ofcourse it show just the Flash drive that isn't in the Array.

    When in normal mode it also works after i Stop and Start the Array manually, but after a reboot nothing works again.

    tower-diagnostics-20230616-1157.zip

  10. Hello everyone, today updated to ver. 6.12 and suddenly my server lost SMB access in Windows 11, but if i STOP and START the ARRAY on Ver. 6.12, so it works fine, but after server reboot the issue is back again, I have searched everywhere but can't find any solution to this problem, if I go back to ver. 6.11.5, so no problem with SMB, all my Shares are available, attached the diagnostics and much appreciate the help

     

     

    tower-diagnostics-20230615-1930.zip

    • Like 1
  11. Hi,  I have looked everywhere for this with no success, tried to change the "rc.local_shutdown" script to remove the "beep -r 2" in the "rc.d" directory but it didn't work as it gets overwritten after the server is restarted .
    My server has a HUANANZHI X99-QD4 with 32GB Ram and an Intel® Xeon® CPU E5-2666 v3 @ 2.90GHz, it has a PC speaker that beeps once when you start and twice when you turn off the server.
    I've also tried disabling the first beep from Unraid by adding "pcspkr.conf" to "modprobe.d" and same thing, it's removed after reboot, I know you can solder off the PC speaker, but I wanted to fix it without removing it.
    In the bios I can't find how to disconnect the speaker either.
    I would be very grateful if someone here could help me with this, thanks in advance

    *Solved this with a new bios from GITHUB user Koshak1013.

  12. On 5/20/2022 at 10:01 PM, serch826 said:

    After many attempts with Onlyoffice through "onlyoffice.mydomain.com" without making it work, I chose instead the LAN address with port 4430 because with this works great and outside LAN also works great with Swag and Wireguard activated, I am satisfied with this result.

    So my last update for this issue, i fixed it very simple, i put the LAN IP ADRESS (in my case: 192.168.1.31) of my OnlyOffice container in the Onlyoffice's subdomain.conf file (/mnt/user/appdata/swag/nginx/proxy-confs/) in: " set $upstream_app" and the PORT 4430 in: "set $upstream_port" and now i can put the "OnlyOffice.mydomain.com" adress in the Nextcloud setting page for OnlyOffice and everything work fine, even the connection is secure through Cloudflare.

  13. Hi, thank you for your Owncloud X, it's working awesome, for me this is the best working on my system, i've tested all the other versions, including the Nextcloud's.

    Just want to ask about the Gallery app, can't get it to work properly, it doesn't show any picture.

    Any help will be appreciate. 

    Thanks!

    gallery.jpg

×
×
  • Create New...