musingcypher

OS and Version: Windows 10 Using file manager to access the share, like \\tower.

Hello, Running Unraid 6.8.0, and the server name is 'tower'. I can't access the share folders using '\\tower'. \\IP_Address_of_tower => works \\tower.lan => works \\Anyname_other_than_tower (say, tower1, tower2, etc) => works http://tower => works \\tower => does not work. Can I get some help troubleshooting this please? I could rename and live with it, but just curious as to what the root cause is. Thanks,

Sweet.. Thanks. This worked and the container is now updated to 1.0.3.2461

I'm interested too..

Sweet.... that was it. I removed the cached credentials and all is good now. Thanks for the help.

I'm trying to access from Windows, but both AFP and SMB are enabled. Disabling AFP and just leaving SMB did not help either.

Attached the diagnostics, can someone help please? Thanks, tower-diagnostics-20160705-1503.zip

Out of no where this issue just started. \\tower prompts for username and password. Only one user (root) on the system, and all shares are public. Did run Tools\new permissions, but no luck. I created a brand new share to test and same story. Anything changed would be, AFP is enabled - I disabled AFP share and still no luck. Restarting tower didn't help either. help please.

For reverse proxy this would help.. I'm doing it now.. ownCloud was installed with defaults. https://www.linuxserver.io/index.php/overview-reverse-proxy-with-docker/ https://www.linuxserver.io/index.php/overview-reverse-proxy-with-docker/installation-of-apacheweb-docker/

I could use some help with port forwarding.. I have onwCloud installed and configured with MariaDB. I can access it within LAN no problem. I have double NAT (cable modem => vonage router => my network router). Forwarding port 80 in vonage router => network router => Tower works and I get the webGUI from outside of LAN. But when I forward port vonage:80 => network router:80 => Tower:8000, and vonage:443 => network:443 => Tower:443, and when accessing from outside LAN with URL - http://domain.duckdns.org results in URL being resolved to https://domain.duckdns.org:8000 but errors as ERR_CONNECTION_TIMED_OUT. Any thoughts? I was going to remove the double NAT and put vonage in DMZ, but since port 80 forward works, I thought double NAT may not be the issue.

Host Thanks!

Hi Everyone, I played around with dockers to figure out why port 80 was being blocked (long story short - couldn't get Apache/Nginx to run on 80). Anyways, figured out emhttp is using 80. In the course, I was playing with the settings and ended up breaking PlexMediaServer/limetech container. It works when changing the network type to Host, but using Bridge and mapping container/host port 32400 does not. My question is (I can't remember how I had it originally), what is the appropriate setting for PlexMediaServer? Bridge being recommended, I was trying to get it work on that network type. Thanks.

That helps. Thank you.

emhttp is using port 80. Because of it, I can't run Apache or Nginx in Bridge mode with mapping to host port 80. What is emhttp by the way? And how do you guys address this issue. Ofcourse, running web servers on a different port is always an option, but anything bit elegant? Is emhttp a http daemon and is able to be configured to serve a static html file? Background is: ownCloud is inaccessible from outside home network. Just looking to see basic thing like serving a HTML file without port forwarding would work, before diving further debugging.

So, got this working. Though all privileges were granted, write to one of the tables failed. Wiped off no restarted, and all is well now. Of course using '%', not local host. Thanks everyone for the help.

I tried that already without luck :-(. After running and update SQL statement, I verified the contents of mysql.user. Even tried having both '%' and IP for the same user, no luck yet.

My suspicion though is, this has something to do with the $CONFIG created by the setup page (/var/www/owncloud/data/config.php). But that is only a speculation at this point. I'm still baffled how the 172.17.42.1 is taken when my IP on the LAN is specified.

I change from localhost to IP. I see the newly granted permissions. Still no luck. I can safely connect to the database using "mysql -u owncloud -p -t owncloud". It prompts for password and I can log in without any issues. I've to admit though, that once (only once) I got past this stage and got to the 'binlog' issue. I fixed 'my.conf' and got back to redo the step and never got beyond the original issue of database connection. I restarted both DB and OC few times though.

Can the permission be verified? MariaDB [(none)]> show grants for 'owncloud'@'localhost'; +-----------------------------------------------------------------------------------------------------------------+ | Grants for owncloud@localhost | +-----------------------------------------------------------------------------------------------------------------+ | GRANT USAGE ON *.* TO 'owncloud'@'localhost' IDENTIFIED BY PASSWORD '*******************************************' | | GRANT ALL PRIVILEGES ON `owncloud`.* TO 'owncloud'@'localhost' | +-----------------------------------------------------------------------------------------------------------------+ 2 rows in set (0.00 sec)

I get error while setting up linuxserver/mariadb in the 'create admin account' page for owncloud. The error is: Error Error while trying to create admin user: Failed to connect to the database: An exception occured in driver: SQLSTATE[HY000] [1045] Access denied for user 'owncloud'@'172.17.42.1' (using password: YES) But the tower IP is 192.168.1.101. Not sure where 172.17.42.1 comes from. The database 'owncloud' is present in MariaDB, and user 'owncloud' with permissions. Posting in linuxserver/MariaDB thread got the feedback that it's likely my ignorance of knowing how to setup owncloud. Can I please get help? Thanks.

If this is a fresh install of Owncloud then this is an issue with you not knowing how to setup Owncloud not an issue with MariaDB. After you pull the docker container you go to the OC webui and there is a setup page for the database. This is what I'm referring to. Incidentally you need to change the binlogging in MariaDB due to a fairly longstanding bug in Owncloud to do with binary logging in MariaDB/MySQL This is not something I've had to do myself as my setup is very different. (Not something I can offer as a solution though) Sequence of install 1. Install MariaDB 2. Change Binlogging 3. Install Owncloud and configure via the webui. Thanks. If you are referring the first page https://<IP>:8000 that pops up when 'webui' is launched right after ownCloud is installed (after installing MariaDB and creating DB and user), then yes, I specified my IP and did not leave it as 'localhost'. Let me post in owncloud thread and see if anyone can give me a hand.

I'm using gfjardim/owncloud.. does that make any difference?

I removed and installing it again.. The section I see are: Add container Volume Mappings Port Mappings Environment Variables Extra Parameters Additional Fields. This is with 'advanced option' enabled. But don't see a place to specify HOST :-(

I'm lost. Where do I specify this though? I went back to 'edit' page of ownCloud, and don't see anything to specify host even in the advanced view. Do I have to reinstall ownCloud docker? On the other hand, if this is in the 'WebUI' of ownCloud, yes I had it as 192.168.1.101, not localhost.

I get error while setting up linuxserver/mariadb in the 'create admin account' page for owncloud. The error is: Error Error while trying to create admin user: Failed to connect to the database: An exception occured in driver: SQLSTATE[HY000] [1045] Access denied for user 'owncloud'@'172.17.42.1' (using password: YES) But the tower IP is 192.168.1.101. Not sure where 172.17.42.1 comes from. The database 'owncloud' is present in MariaDB, and user 'owncloud' with permissions. Any thoughts? Thanks.