Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Closed 8 years ago.
Improve this question
Yesterday I added a custom MembershipProvider to an ASP.NET web application, but when I deployed the application to its remote host server, it failed. I know I had the login info correct, and I also know that for nearly any exception in the login process, the Login control displays the standard error message, "Your login failed", so I assume something is wrong in the code/config.
What can I do to diagnose what is wrong on the server?
BTW: This weekend I only have FTP access to the server, so no event log, and CustomErrors is already set to Off.
THE END: I was an idiot, and using the wrong query window to check if the my login actually existed on the server.
You can try a couple of things:
Set custom errors to off in the
webconfig and look at what error its
giving
Look at the event log to see
if there is an useful info for this
app
If the above are not fruitful, then go for remote debugging!
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
I received a notification from Firebase to reverify my custom domain. Going into the firebase hosting dashboard, I only have one button to press on
Once I press it, I get the error:
We couldn't verify your domain . Please check your settings and try again.
What settings is it referring to?
On the DNS provider side nothing changed. Still have the records as configured when I first set up firebase hosting.
Received official word from Firebase:
We are aware of the deep impact it might be having for your project,
but I assure you we are working on it as our top priority. Our
engineering team is aware of this problem and even though they are
already working on it, the issue is still affecting several projects.
I apologize for the inconvenience and will keep you updated as soon as
more information is available.
[UPDATE]
https://status.firebase.google.com/incident/Hosting/21001
There is now an open ticket
Seems that they have fixed issue.
I just pressed "Verify" button again now and status says "Connected".
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
Apologies if this is in the wrong category. I'm currently developing and application in ASP, due to my inexperience with ASP I'm worried about vulnerabilities that a user can exploit.
My application is being coded from scratch, no templates used or defaults from Visual Studio, completely blank projects. The user is greeted with a login page where depending on there user access in active directory depends on which pages the user can access.
The exploit I'm worried about is if the user will be able to commit a directory traversal and access a page in which they're not allowed to access and change critical information.
I'm afraid my inexperience has caught up with me. Could someone explain to me how I could limit the access to the user or, If I'm over thinking the process, correct me? Constructive criticism is accepted.
Microsoft does try to help protect your application through their defaults, so if you're running in IIS, make sure the user the application pool is running under only has write access to the folders it needs to write into.
This is a very open-ended question and depends on many factors such as version of .net, server OS/IIS version, other handlers installed, etc. But a good start is to review the OWASP Top 10:
https://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project#OWASP_Top_10_for_2013
Here's a list of some automated tools you can use for testing your implementation:
https://geekflare.com/online-scan-website-security-vulnerabilities/
Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 6 years ago.
Improve this question
Currently I am refactoring the site written on ASP.NET MVC5.
It already has published-version on some remote server (Windows Server 2012, IIS). Every time after some code refactored I do publish again and replace some folders\files on remote server.
What I found and want to know if it is a bug or something else :
In Debug mode I can access site only as localhost:**** and it is correct.
After publish everybody can access site by two url : 'sitename.com' (OK) or 'sitename.sitename.com' (Hmm?). 'sitename.sitename.sitename.com' doesn't work - OK. I think this happened because of some settings of IIS\Server isn't it?
It is not the urgent problem, but I want to know why it happened. Currently I can't contact to previous developers, what is the sad moment.
It seems that "sitename.sitename.com" is a subdomaian of sitename.com go to Your hosting provider control panel and deactivate sitename.sitename.com subdomain.
Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Closed 8 years ago.
Improve this question
I am redesigning my company's website. I am not a developer, but have learned as I went along. I am ready to push out my site to a test subdomain, but I can't figure out how to publish it correctly using VS Express for Web 2013. I have multiple problems.
First, we have our own internal IIS server and I have a "site3" folder on the server ready for testing the new site. I can't use Web Deploy or Web Deploy Package. I publish using File System. This seems to sorta work, but no images load and it redirects me to a Login page that I have no intention of using. When I run the site on my local machine, everything works 100% fine - no login page and all site resources load and function perfectly.
Second, when I try to publish, there is no "Release" configuration like I see in online tutorials and MSDN, only "Debug." Is there something I'm missing in the configuration? The publishing? Am I using the wrong framework? This is my first rodeo and I am completely lost.
If anyone wants to look at my completely jacked up site, it's http://site3.tcns.net
EDIT: I'm beginning to think that it has something to do with the fact I have no clue how to configure the web.config file and the default file isn't plug-and-play for a basic website.
I have some idea as to what happened. I accidentally created an MVC solution instead of a basic website.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 8 years ago.
This question appears to be off-topic because it lacks sufficient information to diagnose the problem. Describe your problem in more detail or include a minimal example in the question itself.
This question does not appear to be about programming within the scope defined in the help center.
Improve this question
Having upgraded to version 3.3 I can no longer upload files.
The upload appears to work, progress bar runs without errors.
Metadata can be amended.
When visiting the files URL a 404 occurs.
The file IS NOT written to the uploads directory.
Upload directory has the correct permissions (755)
I'm thoroughly stumped - any ideas anyone?
This issue pertains to the owner of an uploaded file.
In my case the website files were owned by the FTP user, not the web server user. It seems this wasn't an issue in older versions but now is and this caused the problems documented above.