I have a Joomla site running on local intranet. It works perfectly if accessed via LAN. But if someone tries to access the same via VPN network then gives below error.
Access to the Web site is blocked by your administrator. Please notify your system administrator. Made http request for GET /index.php?option=com_content&view=category&id=634:blackberry-&Itemid=59&layout=default HTTP/1.1 to techiecloud:80
What could be the possible reason for the same, Is it application configuration issue or related to network.
That's a network error message rather than a Joomla one.
Try uploading any website there - Joomla or not - and I assume you will get the same message.
Related
we have an IIS 7 server hosting different sites/applications.
Take not that this server is hosting other site/site-applications running on either asp or php. There is already an existing site application running thru fastCGI php.
I now added a new site (not a site-application) - a laravel 5.1 framework, to the IIS server, but this new site is not loading anything. Tried a test php page which echos phpinfo() only and i also made a static html file with just "Hello world" on it but to no avail.
Checked my handlers, and my php handler is there.
When i try to browse the sites host name I get this error:
The server at [mysubdom].[domain].com can't be found, because the DNS
lookup failed. DNS is the network service that translates a website's name to
its Internet address. This error is most often caused by having no connection to
the Internet or a misconfigured network. It can also be caused by an
unresponsive DNS server or a firewall preventing Google Chrome from accessing
the network.
Is this really a DNS problem?
Can you open it local? http://127.0.0.1/{websitename}/index.html with the hello world ... Don't always go directly to your binding address.. try to load on the server itself first.
Is it possible to redirect url browse from same network to local hosting and for other network provider to redirect to other hosting? if it is please guide me how it will done . is it done by programming using php or i need to configure server at cable net . actually i want make website for local internet service provider he want to share vdo and files over his website but problem is that he just want only user from his network can access those files other then that they can just view website but when they try to view video they get error that your are not from same network only user from abc network can view these files
I am writing a PHP app to fetch all my photos with Instagram using their API. However, what puzzles me is, I run the app on my hosted server it works perfectly fine and the same app running locally does not work.
Here are some points on the app workflow:
The user sees the homepage and he will be prompted with 'sign-in with Instagram'
User signs in with Instagram and authorizes the app.
Instagram redirects the user.
The app then makes a request for access_token and receives it.
Using the access_token, the app will send further requests for user media
The response is parsed and the links to the images are now provided to the user.
All the above mentioned process works fine on my hosted server but fails at 'Step 3.' and redirects user to home page of my app.
The problem is localhost being the redirect_uri. Does anyone have a solution to this problem to use the app locally?
P.S: I have registered two separate clients on Instagram: one for locally hosted development and the other on a web server.
Also, I have tried localtunnel. Did not help either.
I know its a very very very old Question. but for those who get to this page hoping a solution:
instagram currently does not allow to use something like localhost or myvhost.test in redirection url, whats more it requires the url to be certified (https).
so the only working solution I could find is using ngrok. you should download it from the url, open it and type a localhost virtual domain name along with a specific port number like ngrok http myLocalUrl.test/app 80, hit enter and it will gives you two temporary public links.
it will remain valid until you close the ngrok command line. you can direct the link to a specific port number and direct the port number to specific folder path of the application in your localhost.
the tutorials provided by ngrok is simple enough if you did not understand my hints.
I was dealing with this issue trying to develop an Instagram App using NodeJS/Express.
I got around this by using my computer's external local IP rather than localhost, which you can grep for. I assume you're on a *nix machine, so do a very simple (and crude)
$ ifconfig | grep inet
which will return you a few ip and MAC addresses, one of them being your external IP. However this is lousy because it means every time you switch IPs you'll have to update your application's redirect_url with Instagram as well as update any code that relies on it.
Thankfully, there exists services like no-ip that will basically provide free DDNS service to you, so you need simply register a hostname with them and then drop that into your DEV env code as well as your development client's redirect url and you're set to go!
I am running a virtual machine on my computer (debian 6.0.2.1) that runs an apache+php+mysql server. On my local machine I have a WAMP stack instaled. On both machines I have CodeIgniter deployed and running a RESTful API.
What I am trying to do is to communicate with my virtual machine from the local machine's application. The virtual machine's application accepts post & get methods for an end-point.
e.g. http:///thumbs/save/ it should return a message. If I test it in the browser for the get method, it runs fine. The problem is when I try to access it from the other application (local machine deploy) with a jquery post/get I get the following:
for chrome as usual: XMLHttpRequest cannot load http:///api/thumbs/save. Origin "http://localhost" is not allowed by Access-Control-Allow-Origin.
and firefox just throws a 200 with status OK but it shows up red and with no response.
A little help would be appreciated. Tell me if you need code examples.
Thanks.
The reason you are seeing that error, Access-Control-Allow-Origin, is to prevent a security issue known as XSS (Cross Site Scripting). Your one domain is localhost, and the other is API.
Take a look at this question/answer for some ways around it. No code examples, so not sure what methods/access types you are using: Access-Control-Allow-Origin error sending a jQuery Post to Google API's
I have a kohana (php) web site and we have a problem with the sessions when used by computers on a local network under a proxy.
The problem:
PC 1 and PC 2 are in the same local network. They use a proxy server to access the external web site.
PC 1 access the site with "USER A", he is in the main page now and the site says "Connected with USER A".
PC 2 enters the site and access with "USER B", he is in the main page now and the site says "Connected with USER B".
PC 1 press F5 to reload the site main page, and the site now says that is logged with "USER B".
The system is installed externally and we have this problem only in this under-proxy network. Access from other PCs also under local networks (but no proxy) don have this problem.
We enabled the "user_token" part in the auth module (it uses a new table named "user_tokens" that uses the browser user agent), but the problem persists.
-- edit --
We are using Kohana 3.0, PHP 5.2.9 and postgres 8.4
Does your proxy support caching? It should NOT cache pages which are different if the client is logged in.
You application may have to set appropriate HTTP headers to tell the proxy that it is not allowed to cache HTTP responses.
If this doesn't fix it, make sure you're not using the client IP address as the Session key.
(If you still fancy using the IP, create a whitelist for allowed proxies, then use the HTTP forwarded_for header. It'll only fix the problem for proxies you trust though.)
Can you turn the proxy off temporarily to confirm the issue?
Can you try accessing the site with Firefox and the Firebug extension? This will let you see the exact HTTP response codes and headers that are being sent from the site. Knowing what they are will help us diagnose the problem for you.