I created a test APP and installed it on my domain. I don't see a link for the Admin Config Url anywhere in my domain's console. If I go to the Settings for my app it just has the Universal navigation links.
The Setup Url also doesn't get called when adding the app to my domain.
Do these settings still do anything?
Finally figured it out. The link has to end in .com (probably other extensions work as well). I was using localhost and the link wouldn't appear.
Related
I'm using Visual Studio 2019 (as Administrator) and IIS Express with the extra Widows 10 features needed to publish web sites on the internet. I created a new Blazor app with the following choices:
Server Side
.NET 5.0 (because .net3.1 does not have ProtectedBrowserStorage)
Authentication - None
Configure for HTTPS (because my domain name uses Cloudflare servers)
Enable Docker - No
Environmental variables
Project properties - None
Windows AdvancedSystemSettings - Development
I did not add any more components nor did I modify the default code.
I built and ran it in release mode.
The web site displayed the home page on a Chrome browser.
I could navigate to the Counter page.
When I clicked the "Click Me" button the current count incremented as it should.
Then I published it to the default file ("~bin\release\net5.0\publish).
I copied this file (with admin privileges) into inetpub and renamed it "B02".
In IIS I created a new web site called B02 specifying the physical path as C:\inetpub\B02.
New App Pool B02 was created and I accepted it.
I did not add a specific user so Test Connection failed but I think this is OK.
I added two bindings
https port 443 IP Address *
https port 443 IP Address 19.168.0.34 (the reserved address of the computer on the router to which port 443 is forwarded. i.e. I'm using port forwarding on a NetGear router)
I could then click, in IIS, "Browse*:443(https) and the web site was OK. I could navigate to any page and all links worked including the "Click Me" button which incremented the counter.
The problem is that when I enter into the Chrome browser the address
"https://www.bkdaniels.com" the web site appears, I can navigate to any of the three pages, the About button works, the "Brief Survey" button works BUT THE "CLICK ME" BUTTON DOES NOT INCREMENT THE COUNT. (It does change the style of the border of the button).
I have presented this simple problem in the hopes that it will enable me to make user interactions work on a custom web app I have written. Presently they all work in IIS browse but not over the internet.
My domain name "bkdaniels.com" is registered with GoDaddy where I have specified to use name servers at Cloudflare because Cloudflare provides and SSL Certificate that prevents clients seeing a warning about the site being not secure.
7/29/22 A solution has been found.
A couple of trivial changes that cleaned up warnings in the Browser console were as follows:
Installed 6.0 SDK
Added to Program.cs - app.UseWebSockets()
These alone did not solve the problem. the Counter click me button still failed to increment the count.
The action that solved the problem was to go to GoDaddy and change the nameservers from Cloudflare servers to GoDaddy default name servers.
I then had to by pass the security warning since I no longer had the SSL certificate that Cloudflare provided. So I clicked "Run Anyway".
The "click me" button incremented the counter.
I will now work with Cloudflare support to find a way to make it work through their nameservers.
8/15/2022 I have now found that a temporary workaround is to set the Cloudflare Dashboard Cache to Developer Mode. This solves the problem with the counter button and also enables my main web site to work. I am still looking for a proper solution.
8/29/2022 SOLUTION
This solution enabled the click on the default Blazor Server app to work and it also enabled my serious web site to work perfectly.
Cloudflare/ logon/ domain name/ dashboard/ speed/ optimization/ auto minify/ HTML / OFF
.
I'm a beginner in Shopify and trouble with Shopify proxy
Front Store: https://bhavin.myshopify.com
App Store: https://myapp.ngrok.io (Laravel)
I want to add two files (custom js and manifest.json) in my front store.
Install and authentication is working fine
I'm adding manifest.json something like that
var link = document.createElement('link');
link.rel = 'manifest';
link.href = 'https://myapp.ngrok.io/manifest.json';
document.head.appendChild(link);
1. Without proxy
manifest.json file added properly but throw error something like that
Access to resource at 'https://myapp.ngrok.io/manifest.json' from origin 'https://bhavin.myshopify.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
2. With Proxy
Subpath prefix: apps
Subpath: cnv
Proxy URL: https://myapp.ngrok.io/proxy
Now my manifest.json file path is https://bhavincb.myshopify.io/apps/cnv/manifest.json
Url is working fine if I'm logged in the admin panel
If I open that URL when I'm not logged in then it returns
This page isn’t working with HTTP ERROR 401
In my front store while load manifest file it is showing something like that (when logged in)
Manifest: Line: 1, column: 1, Unexpected token.
There is not any error in manifest.json
I'm using Laravel Shopify package
As of I know, I guess I'm doing something wrong with a proxy configuration.
Does anyone have a solution?
Any help will appreciate
I resolved to issue my self (ref. 2. With Proxy)
The issue with my store actually I'm using free trial and in free trial you can't disable password protection
If your password protection is enabled and you are trying to access proxy URL without logged in, in that case, Shopify won't allow accessing.
After purchase plan, it's working fine
The better recipe to follow might be this. One, you use your App to access the assets of the shop theme, and upload your manifest.json text file as an asset. That means it is accessible in Liquid, in the theme, and the shop can therefore render it and make it useful.
Second, use your App to install custom.js as a ScriptTag asset. That is the usual way to accomplish running your own JS.
The App Proxy is not really meant for use the way you are using it.
I have uploaded a Magento website to Azure website. It was working perfectly fine with websitename.azurewebsites.net
But when i tried to use a custom domain(I did the dns thing also). Whenever i go to the custom domain or with .azurewebsites.net it redirects to www.websitename.azurewebsites.net
Why is the www coming before websitename.azurewebsites.net ?
You configured your DNS with CNAME
www.websitename.azurewebsites.net
Check the guide you followed for DNS configuration and make sure "www" in the front is removed.
I am trying to point a custom doamin provided by Domain.com to my Heroku app. Everything works well unless I try to enter a direct URL past the normal landing page.
If I go to mycustomdomain.com I get the right landing page and can navigate throughout the site. However, If I go directly to a URL deeper insite the site such as mycustomdomain.com/widgets I get a 404 error. But, if I go to myapp.herokuapp.com/widgets everything works fine.
Another ofdity is that when I go to mycustomdomain.com no matter where I navigate the url is always diaplyed as mycustomdomain.com with nothing ever trailing.
This ended up being an issue with Domain.com's configuration. No matter what I tried I could not get the domain the redirect properly. I switched to GoDaddy and used the exact same configuration and everything worked great.
I have a website that is live and a version that I am working on locally using XAMPP. For some reason every time I try to load:
http://localhost/websitename
or
http://127.0.0.1/websitename
it goes to the internet version. This has only started happening. All services are started. XAMPP is working for all other sites that I am working on locally.
Check your site settings as I believe you're having the url in your website set to the live version.
This can have alot of reasons.
What does your windows host file have for redirect rules (C:/Windows/system32/drivers/etc/host) I assume that you use Windows because you said "xampp", correct me if im wrong)
Check for header(); redirects within your websites php scripts.
Do you have a v-host entry redirecting you to another url in your v-host config of your apache?
Check if you have any hard-coded url's? or redirects? in the project that are redirecting to the live version.