I have read other posts with people having issues with the 404 Not Found error when building their own local version of NuGet.Server. None of them specifically asked about what I am seeing as an issue.
I followed the instructions at https://learn.microsoft.com/en-us/nuget/hosting-packages/nuget-server and get the Default page just like it said. The only changes I made to the web.config were to set the requireApiKey=false since this will be a local server.
When I click on the "Click Here to View Packages", and get the 404 Not Found error, I noticed something on the page. It looks like it is trying to resolve to the same URL that is shown as the link for the Package Manager (https://localhost:44375/nuget), but then adds "Packages". Which might seem okay until you look at the "Physical Path" that is listed. It has a physical folder called "nuget" which is not there and was never created in the instructions or during the install of the NuGet.Server package.
Here is a screenshot of the 404 page.
There was nothing in the documentation about adding that folder, and it was not added when NuGet.Server was installed. Is this a configuration issue that I cannot seem to find, a setup step missed in the instructions or a bug in the NuGet.server ?
Related
I'm getting a TinyMCE error on our admin site after upgrading from 2.2x to 2.3.5. Here are the errors I am seeing:
static/version1599523842/adminhtml/Magento/backend/en_US/tinymce.js net::ERR_ABORTED 404
1bf88a18ad7d25758b55791e3570de1a.js:166 Uncaught Error: Script error for: tinymce
http://requirejs.org/docs/errors.html#scripterror
at makeError (1bf88a18ad7d25758b55791e3570de1a.js:166)
at HTMLScriptElement.onScriptError (1bf88a18ad7d25758b55791e3570de1a.js:1681)
I've deployed the static content, I've cleared the cache, I've cleared all the magemojo cache (redis, varnish, etc...) but I still get this error. I've searched around the M2 forum and the github repo but am not having much luck locating why that file wouldn't be available. Instead of the tinymce.js file, I see a tiny_mce_4 folder in pub/static/adminhtml/Magento/backend/en_US
Any ideas what I may be missing here?
Okay, so I was able to finally figure out what the issue was. I found that a module we had installed needed to be updated as it was using "tinymce". I found this by running the following command against our app/code folder:
grep -rnw 'app/code' -e 'tinymce'
Posting here in case anyone else runs into this issue.
Cloning a project and it looks like it comes down fine, until I look in the references and they all have the yellow warning triangle. Then my Error List shows all the references as Warnings. My application is on Visual Studio 2017 and it is MVC with C# coding using .NET Framework 4.7.2. In my normal application, original, the references are perfectly fine and no errors and it works great. Builds and works fine. Once I bring down the clone is then the references are lost. I've done a build on the cloned version and it shows all the references as warnings.
I've double clicked a reference and received an error popup box of "This project cannot be viewed in the object browser because it is unavailable or not yet built. Please ensure that the project is available and built". It feels like Azuredev-ops is just missing my references and their location. I am the only one working on this, so there should be no conflicts. I've posted and cloned right after posting, with same result. My code and Web configs look just fine. I have cloned on other people's system too, and same problem with this application. FYI, many of my other applications are working fine using the clone. Just 1 application is having issues. My references are separated in that some are Copy Local True while others are False. I've also removed a reference and added it back, and it comes back with a warning as if it were never added.
Warning message for individual reference:
The referenced component 'EntityFramework' could not be found.
I am also seeing errors for NuGet packages not being there, but when I look I see the package folder with all it's components in it.
It says that for all my windows core references. And just warning symbols in my reference folder for other references.
I am expecting no errors when I bring down the clone. I've upload using my machine and cloning should be able to use the same reference locations. It just feels like AzureDev-Ops is stripping my reference links out, and then going I can't find them.
Azure-DevOps clone shows references as warnings
To resolve this issue, you should make sure of the following:
Make sure you have checked those two options Allow NuGet to download missing packages and Automatically check for missing packages during build in Visual Studio:
Make sure you do not check the \packages folder to the source control.
When you clone the project from Azure-DevOps server and get missing reference error, you should use the NuGet command line Update-Package -reinstall in the Package Manager Console to force reinstall the package references into project. Check this thread for some more info.
Note: Especially need to pay attention to the third point.
Update:
Error:Mircrosoft.CodeDom.Providers.DotNetCompilerPlatform.2.0.0
According to the error message, it seems you are not add your packages to your packages source in Visual Studio.
You should publish your custom packages to the nuget feed or you can create you local nuget feed, then add the nuget feed path or local feed path to the package source:
Check this document for some more details.
Hope this helps.
I figured it out. I went to my original and did the Update-Package -reinstall. It came back with the Microsoft.CodeDom.Providers.DotNetCompiler.Platform.2.0.0 not there, but it added one, just not 2.0.0. Then I ran an uninstall of the Microsoft.CodeDom.Providers.DotNetCompiler removing it from my system. Then I posted my original up to AzureDev-ops. My clone came down, not all the references were messed up, some were still, but I did a rebuild and that cleared it up. Thank you to the responses, it pointed me in the right direction.
I'm using the NuGet N2CMS package. I've tried version 2.9.6.8 and 2.9.6.14( and .16)
This is a fresh setup/install. When finishing the setup and navigating to /N2 I'm getting a 404 Not Found from the following:
/N2/API/Context.ash?mode=full
You can see my question on their GitHub here.
Anyone experience this, or have a fix?
bherila from the N2CMS team, was able to help me. It turns out that some of the Nuget Packages do not work out of the box; one of which is the standalone N2CMS package.
I was able to get a new project working using the N2CMS.NoZip (management UI) and N2CMS.MVC packages.
Even with these, you will still need to create and decorate a RootPage and StartPage to get past installation. You can see how I created those in the link I posted in my question
Like the header says I am getting an error when trying to work with Umbraco(6.2.1) back office
This is the error:
I already talked with goDaddy support, they says everything is OK from their side.
I flowed every "tutorial" I could find regarding this.
This is an error I am seeing in Goggle Chrome Console:
I am now clueless about what to do next.
*every help will be much appreciated.
This is the config folder:
This is the -- file -- it self
The error says you have an incorrect TinyMCE configuration. It will be a problem with that component and not the host. There is a [Umbraco support ticket] which suggested this may be fixed in release 6.2, but also a [forum post] where its said this could happen in all versions, when a style-sheet which is registered in the database is deleted.
Are you sure all the files are present in the deployed /config/ folder? Check that there is a /config/tinyMceConfig.config file present.
When using a local NuGet server, whenever I try to install an individual package from that server, all I get is this error: "The remote server returned an error: (404) Not Found."
The packages are all there in the filesystem and the feed itself sees all the packages appropriately. I can even browse the package directly!
What am I missing?
I did just upgrade from NuGet server 1.4 to 1.5, but I've seen this happen before. Touching the package files used to help, but that does not appear to be the case now.
EDIT: Actually, I hadn't seen that exact error before...I've seen this one, intermittently, that touching the package tended to fix.
On Windows Server 2008, I was having the same issue. I switched the Application Pool from "ASP.NET v4.0 Classic" to "ASP.NET v4.0". The install-package command worked fine after the change.
sigh...
http://blogs.thesitedoctor.co.uk/tim/2011/09/02/Nuget+Server+On+IIS6+Returns+404+When+Downloading+Package+After+Upgrade.aspx
EDIT: In case the link ever dies...I am hosting my NuGet server in IIS6, which wasn't set up to properly handle extensionless URLs. And since the semantics of downloading individual packages changed from a direct file link to an extensionless route, I started getting 404s. Adding the wildcard mapping described in the article fixed it instantly.
I've been trying to figure this for a couple of hours...
Checked the IIS logs and discovered that URLScan was blocking the route:
GET /Rejected-By-UrlScan ~/api/v2/package/
URLScan doesn't accept any route not starting with '/'. The best I could do was to remove the URLScan from the list of ISAPI filters for the website in the IIS Manager.
I was having the same issue on Windows Server 2008.
Problem was in my own package MyPackage.nupkg that I saved without version.
MyPackage was visible in PackageManager but it was getting 404 error on install.
Fix:
I saved it with name MyPackage.1.0.0.nupkg (1.0.0 is current version) and problem was fixed.
I had the same problem, srv 2008 R2. Changed the application pool to Integrated from Classic and all works fine now.
My problem was same as image above. I could go to the site on url
http://localhost:3407/nuget/Packages
but not
http://localhost:3407/api/v2/package/{package name}/1.0.0.0
I encountered this error while trying to download Signal-R after update Nuget, however it was just that I had not checked the "Allow Nuget to download missing packages during build" option in package manager settings. Once that was that set it all worked fine again.
It could be this as well -
You are trying to refer to a url like : http://yourdomain/application/nuget/packages
Then you should change it to :
http://yourdomain/application/nuget
This is a common mistake.