EWA from personal website

UncleJohnsBand · 2008-07-27, 10:12 PM

Just curious as to what advantage you gain by using a different web server (rather than the built gbpvr one) for hosting EWA?

Fyvve · 2008-07-28, 03:48 PM

UncleJohnsBand Wrote:Just curious as to what advantage you gain by using a different web server (rather than the built gbpvr one) for hosting EWA?

I just want to be able to goto my website and not use the :port/gbpvr stuff. One of the main reasons for this is that all ports are blocked at my work. So if i could just go to Fyvve.com/gbpvr that would be awesome.

Edit: LOL i tried to type ": Port" there with out the space but it changed it to Tongue

. Hilarious.

rsachoc · 2008-07-28, 06:53 PM

UncleJohnsBand Wrote:Just curious as to what advantage you gain by using a different web server (rather than the built gbpvr one) for hosting EWA?

For me its that I want to make other things available via port 80, not just EWA (webcam being one of them)

haripj · 2008-07-29, 11:31 AM

rsachoc Wrote:I followed this (http://forums.nextpvr.com/showthread.php?t=22346) but was still unable to get it working. Will give up until tomorrow

IIS can be a bit of a pain if you are not very familiar with it. You have to make sure the server knows what ASP.NET application it is supposed to run when you create the virtual directory. If you go into the properties of the virtual directory, under application name it should say gbweb.

As far as permissions, I gave the ASPNET account read/write permissions to the gbpvr directory.

As far as the ASP.NET error, you will have to access your EWA website via IIS from the machine acting as the server to see the details of the error - it is probably related to a missing DLL.

Fyvve · 2008-07-30, 01:32 PM

haripj Wrote:As far as the ASP.NET error, you will have to access your EWA website via IIS from the machine acting as the server to see the details of the error - it is probably related to a missing DLL.

I'll give it a try tonight. But just to be clear, i will be able to see the error message from the host computer even if i am accessing it from fyvve.com/gbpvr? Accessing it from that address is the only way i get an error message but I was under the impression that i would still see the generic error message that i posted a couple days ago as long as i was not accessing it from the internal ip address on the host computer. Or in other words, i thought the only way to see the real error was to make it occur with the "192.168.1.xxx:XXXX/gbpvr" address on the host computer.

(BTW fyvve.com isnt my website im just using it for clarification purposes.)

UncleJohnsBand · 2008-07-30, 10:44 PM

Fyvve Wrote:I'll give it a try tonight. But just to be clear, i will be able to see the error message from the host computer even if i am accessing it from fyvve.com/gbpvr? Accessing it from that address is the only way i get an error message but I was under the impression that i would still see the generic error message that i posted a couple days ago as long as i was not accessing it from the internal ip address on the host computer. Or in other words, i thought the only way to see the real error was to make it occur with the "192.168.1.xxx:XXXX/gbpvr" address on the host computer.

(BTW fyvve.com isnt my website im just using it for clarification purposes.)

You will need to define your site (using your example site) as either fyvve.com/gbpvr or fyvve.com/gbweb. EWA expects to be running in either the gbpvr or gbweb contexts.

Fyvve · 2008-08-01, 01:50 PM

Got it working! Thanks for the help everyone. I finally figured out how to get the actual error i was receiving and it directed me to a MS page. From there it was a pretty easy fix. Here is the error:

Quote:System.Web.Hosting.HostingEnvironmentException: Failed to access IIS metabase.

The process account used to run ASP.NET must have read access to the IIS metabase (e.g. IIS://servername/W3SVC). For information on modifying metabase permissions, please see http://support.microsoft.com/?kbid=267904.

I used aspnet_regiis.exe and it was fixed!

Fyvve · 2008-08-01, 02:13 PM

Now that i have it working i have another question, are there any security risks to having it set up this way? Is it more or less secure than using the "fyvvr.com:3887/gbpvr" method?

rsachoc · 2008-08-01, 09:11 PM

Success, I also have it working.

However the only thing that does not work is when I click record this episode, I get a recording failed even though there are definately no conflicts. Disabling IIS and enabled the GBPVR interface allows me to record again.

Any ideas?

haripj · 2008-08-02, 06:12 PM

rsachoc Wrote:Success, I also have it working.

However the only thing that does not work is when I click record this episode, I get a recording failed even though there are definately no conflicts. Disabling IIS and enabled the GBPVR interface allows me to record again.

Any ideas?

I think this is also related to permissions - especially to the database files - again for the ASPNET account.