I'm setting up a new server on AWS, everything is working as expected. but I recently found out that in order to be elegible for business in my country I need to have the server be local. Is there a way I would reroute the server on request? like point to local IP, but all the rest api/admin panel would show/result AWS server?
This is a new problem for me, have not tried anything.
Related
I'm having a very tough time getting this to work. We are using SSRS to view reports on our internal network. However, I would like to deploy SSRS so users from home can use it since we're working from home more frequently. I will supply a screenshot of the current config with the App Proxy settings and maybe you can point something out that I am doing wrong because I'm lost at this point and google has stopped helping.
At this moment, I am trying to deploy SSRS using App Proxy from Azure, however, if you know another way, please let me know.
Again, this is a simple deployment. We simply access SSRS using a http/s address internally and it works fine. I just want users to be able to use it from Home through a website.
App Proxy Settings
App Proxy Cont.
This ended up being a bit of a journey.
Do not install your AD Connect or App Proxy connectors on a Domain Controller. Put them on the same virtual server by themselves.
Set up your SQL Server and Oracle all under a domain service account. If you haven't done this already, get ready to reinstall because it's likely that manually switching the SPN keys isn't going to work.
Leave the default App Proxy settings alone when you Configure App Proxy.
If you have a weblink like reporting.domain.com/reports in Azure you MUST make sure you have reporting.domain.com/reports/ do not forget the extra / at the end.
App Proxy with SSRS will now work.
Use this as your overall guide
https://learn.microsoft.com/en-us/power-bi/report-server/azure-application-proxy
We have 3 servers: a gateway machine, and 2 other hosts (old and new).
Originally, the gateway machine was serving a django app hosted on OLD via proxypass. We are shutting down OLD and have moved the app over to NEW.
On NEW, the app works fine when accessing the host directly (http://IP.FOR.NEW/site)
However, when trying to access via the gateway (so that users don't have to update links/learn an IP/etc), accessing via http://gateway/site gives an LDAP error.
HOWEVER, it's not LDAP that's the issue. The OLD server used LDAP, while the NEW server is simply using the django user system. As a result, all LDAP references were removed, and it works when accessing it directly.
It looks like when accessing via gateway, it is serving the old code but trying to point it at the NEW server. If I stop apache on the NEW server, access via the gateway fails with 'service unavailable'.
As far as I can tell, caching is not enabled on either server.
edit: I tried changing the user facing url (gateway/foo to gateway/bar) which is redirected via proxypass to NEW/site. No change. Still appears to be serving old code on the NEW server.
Any suggestions on where to start looking would be appreciated.
When using the transfer tool on WHM to move an account from one server to another does the old server website still remain live in the process?
Transfer process will not terminate your account from old server. You will have to update your domain nameserver so that your domain will be resolve to your new server.
Transfer tool will help you to copy content, database from old server to new server. Once you copied all data then you need to point domain DNS to new server i.e IP and Nameserver and then website will start running from new server post DNS propagation.
If I log in to our web server using RDP, I can't access any of the sites we run on that web server via their external url. For example, say my web server hosts www.example.com, when I log in to the web server, bring up a browser and try to go to www.example.com, I can't see it.
However, one of our sites was configured in some way to work like this, if I try to go to that url, it works as you might expect.
Unfortunately, this was done by our server hosting partners, who we are no longer in contact with. Does anyone know how this can be achieved?
You can do it in many way..
It depends on your network configuration, but it could also be a simple row in hosts file or a static dns record or a specific route for that ip address.
if you're using IIS you should also set the website to "listen" on the loopback interface in the bindings menu.
or, for IIS 6:
I have two applications with a single domain name (www.domain.com and test.domain.com).
First one has been developed in .NET 2 and the other one with .NET 4.
I have configured Web.Config as these steps:
I've set the same machine key for both of them.
I've set the cookie name.
I've set the domain name to "domain.com".
Also, I've set hard-coded cookie domain name to "domain.com" .
Everything was working fine when both of them were running on a single web server. Recently, I've been asked to move test.domain.com to another server. After moving, authentication ticket is not valid on the second server.
I tested both of them on a single server again and everything was working fine, but in two servers users can't access to test.domain.com. (Authentication Ticket is invalid)
Edited:
The second server is a virtual (VMWare) server. I don't have any problem in physical servers.
I checked the server's time to be synchronized. I also used Fiddler to see if the server does not get the auth ticket and their ticket is sent to the 2nd server.
Note: Servers are located in different networks and maybe proxy or firewall causes this (I've no idea)
Is there anything I missed?
Finally I've found it here:
http://weblogs.asp.net/scottgu/archive/2010/09/28/asp-net-security-update-now-available.aspx
One of ther server was not update, after installing the patch the issue solved!