Pretty simple actually, when the webapp is installed it tells me to go to http://owncloud, which sends me to owncloud.(myusername).com. This ends up as a page not found, and I have no idea how to fix it. Any insight would help greatly.
Thanks
Cannot access owncloud after install (X-post from apps)
Re: Cannot access owncloud after install (X-post from apps)
Clear the cache in your browser. Unless you followed the wiki guidance to expose it outside your network, the link as described will not work.
ßîgƒσστ65
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
Re: Cannot access owncloud after install (X-post from apps)
nope, exact same error, which specifically is: Oops! Google Chrome could not find owncloud.(myusername).com
I have confirmed this with multiple browsers
I have confirmed this with multiple browsers
-
- Posts: 134
- Joined: Sun Mar 07, 2010 9:54 am
Re: Cannot access owncloud after install (X-post from apps)
Please see this ownCloud wiki page below instruction step "Now to test ownCloud to see if it is running and logging in to the "admin" user ID is important at this point. Here is some access information that will be needed." for URL details.
Re: Cannot access owncloud after install (X-post from apps)
sorry about the trouble its causing everyone, but it still does not work, even after logging in and doing it from the server, or from any client. Same page not found error.
-
- Posts: 134
- Joined: Sun Mar 07, 2010 9:54 am
Re: Cannot access owncloud after install (X-post from apps)
do you have other Amahi applications installed? if so, are they working? or is this the only one?
Re: Cannot access owncloud after install (X-post from apps)
The only amahi app installed, an di just tried installing logmon, same error, and... well.... yeah. any tests you want me to run? as a note that i just saw now, i gt this when using apt-get to install, now its removed:
Code: Select all
Reloading web server config apache2 apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1 for ServerName
[Mon Mar 11 21:43:24 2013] [warn] NameVirtualHost *:80 has no VirtualHosts
[Mon Mar 11 21:43:24 2013] [warn] NameVirtualHost *:80 has no VirtualHosts
[ OK ]
-
- Posts: 134
- Joined: Sun Mar 07, 2010 9:54 am
Re: Cannot access owncloud after install (X-post from apps)
Have you tried following the Amahi Interactive Troubleshooter yet (http://amahi.net/)?
Also you should probably try a simpler Amahi application such as, "https://www.amahi.org/apps/linfo", before you dive in any further.
Also you should probably try a simpler Amahi application such as, "https://www.amahi.org/apps/linfo", before you dive in any further.
Re: Cannot access owncloud after install (X-post from apps)
linfo throws up the same error, and the troubleshooter throws up the " Your hda dns server is not working for local hostnames" error. however i staill am able to go to http://hda/ and it works.
this is the output after running suggested commands
ugh, thats waaaaayyy too much stuff. I feel that the number of devices connected over one month is definitely not this high.
this is the output after running suggested commands
Code: Select all
root@Sirius-1S:/var/hda/web-apps/owncloud/html# nslookup hda
Server: 192.168.0.2
Address: 192.168.0.2#53
Non-authoritative answer:
Name: hda
Address: 67.215.65.132
root@Sirius-1S:/var/hda/web-apps/owncloud/html# cat /etc/issue
Ubuntu 12.04.2 LTS \n \l
root@Sirius-1S:/var/hda/web-apps/owncloud/html# cat /etc/resolv.conf
search dhash.com
nameserver 192.168.0.2
root@Sirius-1S:/var/hda/web-apps/owncloud/html# ifconfig | grep -A 5 eth0 | grep inet
inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: 2002:6a33:b021:0:780e:5654:762f:4573/64 Scope:Global
inet6 addr: 2002:6a33:b021:0:21e:67ff:fe64:8251/64 Scope:Global
inet6 addr: fe80::21e:67ff:fe64:8251/64 Scope:Link
root@Sirius-1S:/var/hda/web-apps/owncloud/html# service bind9 status
* bind9 is running
root@Sirius-1S:/var/hda/web-apps/owncloud/html# cat /etc/bind/named.conf
# automatically generated file by hdactl
options {
listen-on-v6 port 53 { ::1; };
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
memstatistics-file "/var/named/data/named_mem_stats.txt";
forward only;
forwarders { 208.67.222.222; 208.67.220.220; };
listen-on port 53 { 192.168.0.2; 127.0.0.1; };
allow-query { trusted; };
};
acl "trusted" {
localhost;
10.8.0.0/16;
192.168.0.0/24;
};
logging {
channel default_debug {
file "data/named.run";
severity dynamic;
};
};
key "ddnskey" {
algorithm hmac-md5;
secret "8zaPJsiw9tOh2JFv4xiArw==";
};
view "internal" {
match-clients { trusted; };
match-destinations { trusted; };
zone "dhash.com" IN {
type master;
notify no;
file "dynamic/hda-n2a.conf";
allow-update { key ddnskey; };
check-names ignore;
};
zone "0.168.192.in-addr.arpa" IN {
type master;
notify no;
file "dynamic/hda-a2n.conf";
allow-update { key ddnskey; };
check-names ignore;
};
# NOTE, you can create a file /etc/named.conf.local and it will be automatically included here!
# WARNING - you better not break the format though!
};
root@Sirius-1S:/var/hda/web-apps/owncloud/html# netstat -an | grep :53
tcp 0 0 192.168.0.2:53 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN
tcp6 0 0 ::1:53 :::* LISTEN
udp 0 0 192.168.0.2:53 0.0.0.0:*
udp 0 0 127.0.0.1:53 0.0.0.0:*
udp 0 0 192.168.0.2:50126 192.168.0.1:5351 ESTABLISHED
udp 0 0 192.168.0.2:44782 192.168.0.1:5351 ESTABLISHED
udp 0 0 0.0.0.0:5353 0.0.0.0:*
udp6 0 0 ::1:53 :::*
udp6 0 0 :::5353 :::*
1302111304 ; Serial
28800 ; Refresh
14400 ; Retry
3600000 ; Expire
86400 ) ; Minimum
IN NS hda.dhash.com.
IN MX 10 hda.dhash.com.
* IN MX 10 hda.dhash.com.
h001 A 192.168.0.1
hda A 192.168.0.2
h003 A 192.168.0.3
[b]... (this was put here by me, it was everything from h004 to h253 with the associated ip, same as corresponding number)[/b]
h254 A 192.168.0.254
hda A 192.168.0.2
search A 192.168.0.2
setup A 192.168.0.2
calendar A 192.168.0.2
help A 192.168.0.2
router A 192.168.0.1
owncloud A 192.168.0.2
$TTL 86400
@ IN SOA hda.dhash.com. root.dhash.com. (
1302111304 ; Serial
28800 ; Refresh
14400 ; Retry
3600000 ; Expire
86400 ) ; Minimum
IN NS hda.dhash.com.
IN MX 10 hda.dhash.com.
* IN MX 10 hda.dhash.com.
1 PTR h001.dhash.com.
2 PTR hda.dhash.com.
3 PTR h003.dhash.com.
[b]... (put here by me, well, you get the point. same as above.)[/b]
253 PTR h253.dhash.com.
254 PTR h254.dhash.com.
Re: Cannot access owncloud after install (X-post from apps)
Is your HDA acting as the DHCP/DNS server for your network?
ßîgƒσστ65
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
Who is online
Users browsing this forum: No registered users and 42 guests