(imported topic written by rnkatpsu)
We have recently moved Web Reports from the BES server to a web server for a number of reasons. All seems to be working well, except for the Wake on Web functionality. When I try to run the report, I receive the error “The Web Reports domain and BES Server domain must match. Wake up requests cannot be sent from this domain.”
Has anyone found a way to get WOW to work in this situation?
Cheers,
Russ
(imported comment written by cstoneba)
I have the same problem. The error is saying that the BES Server domain is using our fqdn of the server, but the web reports domain is just the hostname of the server, however they actually all reside on the same server.
(imported comment written by BenKus)
Hey guys,
This is a built-in security limitation to prevent cross-side scripting of the browser and of the flash player that is used for the report… We currently don’t know a way to prevent this because the restriction is not under our control.
Some more info: The BigFix Server is in charge of accepting wake-on-lan requests and routing them to the right locations. We built a web report (built in flash) that would allow the web report issue the request using SOAP over HTTP. This works great if the two servers are on the same computer… however, if they are using different FQDN, then Flash (and javascript and other web technologies) will specifically block the request because it is considered a “cross-side scripting” issue…
So until we figure out a new way to do this function, wake-on-web will only work if the fqdn of the BigFix Server matches the fqdn of the web reports server.
Ben
(imported comment written by SystemAdmin)
Ben,
We have the same issue and the BES server and Web Reports server ARE on the same server. As cstoneba said - The error is saying that the BES Server domain is using our fqdn of the server, but the web reports domain is just the hostname of the server, however they actually all reside on the same server. There’s got to be a place we can go in and edit the name so they match.
(imported comment written by MattBoyd)
jspanitz,
I ran into a similar issue: http://forum.bigfix.com/viewtopic.php?id=188
If your intention is to set the web reports domain to the FDQN, you could open the registry and look for “Hostname” value in this key: HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\Enterprise Server\Installer . If the value of “Hostname” isn’t the fqdn, you could try changing it.
(imported comment written by SystemAdmin)
boyd,
thanks. for some reason I though the value was held in the database. interestingly enough, the entry is a fqdn. so i guess web reports is using the short :(. I guess I will change the reg entry to the short name and see what happens.
thanks!
John
(imported comment written by cstoneba)
same here. My reg key on the BES is showing the fqdn. Jspanitz, you try it first and let me know if changing it breaks anything 
(imported comment written by MattBoyd)
Well… perhaps this is what you’re looking for? http://forum.bigfix.com/viewtopic.php?id=3604
If you access Web Reports using the FQDN URL, do you get the same error?
(imported comment written by cstoneba)
Same error message, but now the only difference is that the BES Server domain is in capitals and the webreports domain is not:
The Web Reports domain (http://server.fqdn) and BES Server domain (http://SERVER.fqdn) must match. Wake up requests cannot be sent from this domain.
(imported comment written by SystemAdmin)
Boyd - Oh Yippie. It works now. I guess that was kinda obvious - using the fqdn in the url. Thanks for the thinking! I do love the BigFix user community.
Cstoneba - I was just about ready to trash my production server for you But Boyd saved the day. Perhaps changing the reg key to upper or lower case to match would solve your problem. But you gotta test that one on your own
(imported comment written by tscott91)
I cannot get this working! I have the same exact issue as cstoneba posted in #9…
“The Web Reports domain (http://server-fs.some.name.net) and BES Server domain (http://SERVER-FS.some.name.net) must match. Wake up requests cannot be sent from this domain.”
How can I get this fixed? Thanks!
(imported comment written by SystemAdmin)
Hey tscott,
The domains and protocols must patch due to cross site scripting restrictions, however this particular case is a bug (casing doesn’t matter for cross site scripting, but the report thinks it does).
There is a bug for this, and i believe it has already been fixed for our upcoming v3 release of power management.
In the mean time, you can use the solution boyd suggested in post #5, and for the domain to be lowercase.
-Zak