I'm doing a ASP.NET project currently, and I want to upload up in AWS Elastic Beanstalk. So I have all the prerequisite downloaded, installed and setup already, I used Visual Studio 2017 to publish my solution to AWS. There were no errors while uploading, however, when I click on my website link xxxxx.elasticbeanstalk.com, it showed me 403 error.
There were no errors while creating env nor uploading the project onto AWS.
Try to change the url for example, if your url is xxxxx.elasticbeanstalk.com try to add the extension of your index file that you uploaded in your ZIP file.
Example:
xxxxx.elasticbeanstalk.com/index.html
Hope it helps
Related
We store test report site in Artifactory as a jar file. We use the "Allow Content Browsing" to browse the html format reports. We are unable browse anymore anything within the jar file. We are getting a 404 resource not found error. We have self hosted instance.
http:///artifactory//org//latest-SNAPSHOT/site-jarfile.jar!/allure-maven-plugin/index.html
I am using Asp.Net Standard version 4.7 with MVC and attempting to deploy to IIS Express. I am facing several issues in the configuration and cant seem to find straight forward documentation for asp.Net standard. I added a website named localHost aside from Default Website in IIS. I am facing 2 issues.
When I click browse from IIS, it navigates http://localhost/Views/Home/Index.cshtml I get a 404 error.
Server Error in '/' Application. The resource cannot be found
When Debugging From Visual studio 2019 I get
Process with Id of xxxx cant be found
.
Description: HTTP 404.
I am thinking there some port configuration issue but I am unclear on how to configure.
I attached screenshots of my configuration settings.
Please follow Microsoft guideline.
You are trying to access wrong Url. Try below url to access:
http://localhost:8080/Home/Index
Maybe you are misunderstand MVC, you should visit a restful path in mvc instead of cshtml, just like this: http://localhost:8080/Home/Index -> to find /Views/Home/Index.cshtml in you solution.
To host the site .net application you need to publish it and use that publish folder as site folder path in iis.
1)open visual studio, select your project.
2)right-click on your project and choose publish:
3)in publish target select folder and create a new folder in c or another drive where can you access the folder.
4)click on the publish
5)open iis and create a new site
6)choose the folder path and site binding
7)browser your site.
Note:
Assign iis_iusrs and iusr full permission to the site folder. you need to set the physical path credential with your Gmail account.
I am using nexus2artifactory tool to migrate from Nexus to Artifactory. In the initial setup menu, while giving the artifactory URL, Nexus2Art migrator tool is showing below error:
Unable to access artifactory URL. and errors in lines 435,548,473,407,556 of urllib2.py
HTTP Error 503 : Service unavailable
Artifactory URL is accessible in browser and running successfully. But the tool is not able to recognize artifactory. I have checked the log files artifactory.log, request.log, access.log and there is no errors in the log files. Please give me suggestions to resolve this issue.
In web application, i created a site and place the code in my domain [using filezilla i upload the my pages in my domain ]. i place my folder which contain the code in domain like
BusinessEntity Folder, BusinessLayer Folder, DataAccess Layer and my code Folder. my web.config is my code folder. but when i type my url it is giving 404 error. Can you help me to solve this problem. Thank you.
404 - Not Found error. Some resource can't be obtained. Open Fiddler or any other web debugger and check what request return 404 error. After that check existing a resource corresponding to Url
Please check all these things are done properly
Publish the project from your local machine (using visual studio)
Upload the published project to the server.
Create a virtual directory in iis (in the server)
Map the virtual directory to the project folder (means select the physical directory as the project folder)
Do the necessary configuration changes (conection strings or appsettings)
Give write permission for the upload folder and error folder (If you use any)
Checkout http://www.advancedinstaller.com/user-guide/tutorial-iis.html
I'm trying to get an automated deployment working from a CI server (TFS 2010)
Basically I've got a package getting built and if all the tests past I'd like to deploy it.
Outside of TFS and just using the visual studio command line, I navigate to the folder location of the package and use the following:
C:\site\Package>site.deploy.cmd /Y
/M:"https://WebServer:8172/MsDeploy.axd" -allowUntrusted /U:username
/P:password /A:Basic
Where in this case the user is a domain user with full permissions on the destination website folder. When I run this I get a 401 unauthorized error. I've created an IIS Manager and set up the permissions for the network service account on the destination files too but that also gives the same error.
The frustrating point is that from the VS 2010 right mouse click publish page it works perfectly with either user. Does anyone have any ideas. I've been all over stack overflow and I'm certain that the folder permissions are correct and that IIS is configured correctly. The fact that VS 2010 can publish with the same credentials backs that up for me.
I did see that you can pass ?site=SiteName when specifying the server but I just get errors about not expecting that parameter.
Looking at the site.deploy.cmd and site.SetParameters.xml it appears that it certainly looks likes it's going for Web Deploy 2 and that the configuration settings have been correctly grabbed from the config transform.
Thanks
If it's a non-admin user, you need to include the IIS site in the remote URL.
C:\site\Package>site.deploy.cmd /Y /M:"https://WebServer:8172/MsDeploy.axd?site=Website Name" -allowUntrusted /U:username /P:password /A:Basic
It's possible the generated cmd file does this for you, but only when you supply a certain argument.
http://www.jrjlee.com/2011/12/deploying-web-packages-as-non.html
this may work. append your site name with querystring to your url