I try to access my localhost from another pc, through IP address in the same network (10.0.0.6). When I type this address in the pc that runs wamp, I can access - but when I do it in my laptop or smartphone, I get this 403 message:
Forbidden
You don't have permission to access / on this server.
I am using WampServer 3.0.4 as mentioned above, Apache/2.4.18 (Win64) PHP/5.6.19 and MySQL/5.7.11 on Windows 10 (64 bit) with AVAST Antivirus and using "Test Mail Server Tool" on port 25.
I already tried these Q&A and didn't worked:
WAMP 403 Forbidden message on Windows 7
403 Forbidden Error. Hosting a website on my PC with WAMP?
I also tried few tutorials, one of them is this one and, of course, tried the "put online" button, which changed one line in httpd.conf from Require local to Require all granted automatically when I pressed it but still nothing, on the laptop and smartphone.
What else can I do? I just upgraded from 2.5 to the latest release on their website (late but finally). it's really frustrating me... any help or idea?
p.s: I don't have static IP for localhost to access from another device, because my ISP not allowing it (it costs money) so I'm using dynamic ip or using my pc name in order to access. in wamp2.5 it worked well
UPDATE: I tried to disable AVAST Firewall for 10 minutes, and it doesn't show 403 anymore, but also doesn't show anything else (only timeout error). perhaps it's the firewall?
Thank you all and, again, excuse me for my english (if I had any misspellings)
Related
I am trying to configure JDBC but kept getting the same error I am getting using snowsql:
250001 (08001): Failed to connect to DB. Verify the account name is correct: JG3409.canada-central.azure.snowflakecomputing.com:443. 000403: 403: HTTP 403: Forbidden
If the error message is unclear, enable logging using -o log_level=DEBUG and see the log to find out the cause. Contact support for further help.
Goodbye!
I have configured the config file, and I have double checked the account, company, region, reset password to only use alphanumeric.
I have used both forms of the URL
The only possibility is that I am using a trial account, but I can't imagine that this would limit external non-browser connections?
I use a simple user/password, I have whitelisted my IP and I don't have a problem with a proxy or a firewall. I can successfully connect using a browser.. using:
https://app.snowflake.com/canada-central.azure/jg63409
Important contents of the config file:
[connections]
accountname=JG3409
#accountname=uegxydq-pz20606
region=canada-central.azure
username=ASHSNOWFLAKE
any ideas?
Your account is not JG3409 but JG63409 based on this link:
https://app.snowflake.com/canada-central.azure/jg63409
Try in your browser:
https://jg63409.canada-central.azure.snowflakecomputing.com
I found out using snowcd that my computer could not connect via my home router.
When I used my personal hotspot on my (5G) phone, snowcd passed all the tests immediately. The problem then arose how to adjust the network security policy to allow a CIDR block of network addresses through since my phone uses a new address every time I connect, and I can't edit the policy to allow my phone while connected via my phone (for obvious reasons)
Catch 22
123.45.0.0/16 is not accepted in the new Snowflake UI, and 0.0.0.0 doesn't work for me, but the documentation gave me a clue.. the new UI doesn't separate by commas, so I switched to the old UI and voila!
Incidentally the OLD UI uses the same URL as SnowSQL so I picked up my error in my account number there as well (although I should have seen it earlier).
Diabolical but thanks #Sergiu too!
I've had a website running on Azure now for a while, and I've not had any problems until today when I discovered that browsing to it via a mobile device (tested on Android (Chrome/Firefox) and Apple (iPhone 6 - Safari) ) I get a:
You do not have permission to view this directory or page
error. I've not changed anything on the site, the last publish was 5 days ago, and it was working then. Both my staging and prod environments have gone down like this.
It looks like it's returning a 403, but I can't see why.
The site is an ASP.NET MVC5 site, running as an Azure Web App.
Update
OK, I've now run up a test version of the site with the [RequireHttps] attribute removed from the controllers - now I can navigate to the pages by just http, but https gives me the permission error.
I've managed to solve the problem, in my web.config I had a URL rewrite to prevent SSL3.0 access (based on this post: Disabling SSL3 in in Azure websites).
After switching on the logs in Azure and loading the pages up I saw the 403 error with the message
SSLv3 connections are forbidden by this site
in it. This came from the url rewrite.
My PC was happy loading as I have BitDefender and that was injecting it's own SSL cert into place over the one supplied by my site. Turning off SSL Scanning in BitDefender gave me the error on all browsers.
So the solution so far is to remove the SSL3 rewrite and look into another way to achieve the same thing.
I installed the spicework window setup on my server 2008. Here is the URL http://ffrsdevserver.com:9675/portal for my dev server. It works fine on my(Indian) system, other systems of my company, my mobile device with 3G network.
My client in USA said it not worked for him. I verify this by login to server located in USA. on server's browser i got error ERR_CONNECTION_TIMED_OUT Can anybody suggest how can i fix it, I searched a lot on google and spicework community but nothing worked for me.
I found that my port 9675 was closed. I open the port and it fix my problem. Thanks :)
i have tried to deploys the MVC Application in IIS Server (Windows 7 Ultimate (32 bit)) i have configured my web site in localhost:81 is perfectly working. when i have use my computer name : 81 (Server-PC:81) is showing Service Unavailable HTTP Error 503. I have entered the same url (http://Server-PC:81) in network connected System is showing Web page as not found
Please notify me if i have missed any setting such as firewall etc in my pc or any other step i need to do. thanks in advance.
I'm currently receiving
{"code": 400, "error_type": "OAuthException", "error_message": "No matching code found."}
while attempting to get a user's access token on one of our servers. This is occurring while using the REST Client Chrome extension and from our web application, on one particular server.
I am able to receive the user's access token from my local machine and a different server using the same code and extension.
Could our IP have been blacklisted from receiving access tokens? Has anyone else run into this issue?
Thanks,
EDIT
Heard back from Instagram support, this was an issue on their end and has been fixed. Thanks for the help.
Yes your intuition is correct. It is likely that you made too many incorrect API calls that Instagram disabled your IP. I started dealing with Instagram API this week, at the beginning it was working but today I started getting the same error you got. The code also works fine locally or on any other machine. The only explanation to this is that my IP is blocked. Just switch your IP and you should be fine!
SOLVED:
The reason for this error is the ip address from which you are trying to connect to Instagram and get access_token. After contacting my network provider and changing my ip everything got fixed.
To figure out if your issue is caused by your local ip (not the server ip) try to connect to your app via mobile network or any other network different from yours:
- If it works you need to change your local ip.
-If it does not work - change your server ip cause it is probably banned by instagram for lots of malicious requests.
I was having the same trouble: users couldn't authenticate through Instagram and the error returned was "OAuthException" and "No matching code found." Started on 4/28/15 but didn't catch until two days later. Only in production, not staging, so it was almost certainly IP.
I posted to the Instagram developer help center (https://help.instagram.com/contact/438525166257277) yesterday at 7pm and the problem was fixed by this morning, with a cryptic email from their support at 11am ("The issue has been resolved").