AppleTV 2 (black) Adding a HTTPS source for the library

I have a home server running Windows Home Server 2011 that I am using to store my media. I can add videos and music just fine using SMB. With WHS 2011 I have setup a web domain to access my server from the internet. I can access it from computers outside of my network but when I try and add the source in XBMC (tried on AppleTV 2 and on a PC running Windows 7) but it won't connect to the server. It doesn't even seem to actually try and look for it but immediately says that it cannot connect. When trying to connect I have tried HTTPS and HTTP but with no success. It seems like the issues is on XBMC as I am able to access the server via the internet on several different computers. Any ideas or help would be greatly appreciated.

Added source looks like this?
http(s)://username:password@mydomain.com:port//folder/subfolder/file.mp4
Because for XBMC to scan it needs to see folders (with either sub folders or files) instead of running into some software program.

Correct, when I add the source:
Protocol: web server directory (https)
server address: my domain.com
remote path: (blank)
port: (port)
Username: (username)
Password: (password)

The way that I set up my domain is that with a specific username i only have access to my 3 movie folders. I would like to add all 3 of them to my video source.

Even when I add the folder names in the remote path it isn't able to find it.

I am also trying to get this type of setup working. Currently i have Windows Home Server 2011 hosting a centralized Mysql database with 2 x ATV2(black) running Eden. I would like to somehow access my library over the internet using either webdav or https. Anyone have luck setting this up?

Try giving it a folder name in remote path like so:
/downloads/

That would be the name you gave your folder instead of "downloads" of course.

Then click ok, scroll to the new entry and click on it. Now you should see folders on your share. Then set the content.

But i am pretty sure you have the path wrong or some firewall is blocking you.

@ramdodger your problem is not the same, plz start a new thread for the problem you are having.

I'm having a similar issue, but only with https. I'm using a DynDNS service from afraid.org, and I can connect using my afraid.org with HTTP just fine.

12:08:09 T:2897736384 DEBUG: CFileCurl::GetMimeType - https://me:pass@my.site:443/media/tv -> failed
12:08:09 T:2897736384 DEBUG: FileCurl::Open(0xbfffb8cc) https://my.site:443/media/tv
12:08:09 T:2897736384 WARNING: FillBuffer: curl failed with code 35
12:08:09 T:2897736384 ERROR: CFileCurl::CReadState::Open, didn't get any data from stream.
12:08:09 T:2897736384 ERROR: GetDirectory - Unable to get http directory
12:08:09 T:2897736384 ERROR: GetDirectory - Error getting https://me:pass@my.site:443/media/tv

Copy/pasting those curl links into a browser works fine. Using XBMC with my server's local ip 192.168.1.10 with https also works.

I'm running Ubuntu 11.10 32-bit with Apache2, if it matters.

@DDM123
Maybe the certificate?

Generate a new SSL for the server with the server FQDN in the certificate.
Also change the ServerName entry under the VirtualHost directive.
Change it from localhost to the same FQDN as you use to access the server and you have defined in the certificate.

Or try to make it work as http first, then add the ssl.

Instead of using HTTP, why not setup a VPN to your local network?

If you're using a windows machine, there's a really easy utility called Hamachi that can setup a VPN pretty easily.

Cool, thanks for the responses. I'm going to try out regenerating my cert shortly. I actually have a L2TP VPN running, but I travel a ton and it'd be nice to not have to worry about firing up my VPN every time I ran XBMC on my laptop, iPad and Android stuff. It can be done though so this isn't a huge problem. L2TP is super slow on my Android over 4G for some reason, whereas PPTP isn't, and PPTP is flaky whereas L2TP isn't.

(2012-07-21 08:22)MassIV Wrote:  @DDM123
Maybe the certificate?

Generate a new SSL for the server with the server FQDN in the certificate.
Also change the ServerName entry under the VirtualHost directive.
Change it from localhost to the same FQDN as you use to access the server and you have defined in the certificate.

Or try to make it work as http first, then add the ssl.

A new cert plus the directive totally worked and you are my new favorite internet person.