Pub get in flutter not accessible. what are all the urls need to be whitelisted in corporate policy.
I am using android studio
Related
I have the Sonos Acme developer test service setup and running but my Sonos Player doesn't seem to be able to connect. I'm wondering if a TLS SSL certificate is required no matter what even in a sandboxed environment.
I'm running the java service on a remote AWS instance behind a domain. The service is setup with the default installation details. It does not log any sort of connection attempt once I add the service to the Sonos player via customSD.
Accessing the Sonos Player via customSD and adding the Acme service does respond with Success! But again it doesn't show up in the service list. Manually pulling the WSDL does work correctly via the http request.
Also to note that Sonos seems to be in the middle of creating it's new developer portal and since last Monday ( June 24th ) the new portal no longer references the Acme test service. I'm wondering if this is due to it no longer being valid and it's documentation out of date (est. 2017-2018).
I expect the service to show up in the Sonos Controller when adding a new service but it doesn't appear and the log doesn't show any attempts to connect.
An SSL endpoint is required for production, but you can use a non-SSL endpoint for testing. See the comments in this answer for details: With a Sonos player, adding local service to customSD does not show up Music Services
I have setup jenkins server on aws and provided access to only my org public IP.
I want to open it with my organization vpn for some people working from home so he want access the server.
Also jenkins have google auth.
how to setup for this problem
I want to be able to expose my local machine address to the internet to be able to work with:
Google OAuth2 flow;
Receiving Push-Notifications for changes in my calendars/events;
So that, I need some tool that will expose my local machine URLs to the Internet so Google will be able to use this web hooks.
I found that ngrok with basic(5$) subscription works for me. Free versions doesn't work since I need SSL as it's required by google:
This is your Webhook callback URL, and it must use HTTPS. Note that
the Google Calendar API will be able to send notifications to this
HTTPS address only if there is a valid SSL certificate installed on
your web server. Invalid certificates include: • Self-signed
certificates. • Certificates signed by an untrusted source.
• Certificates that have been revoked. • Certificates that have a
subject that doesn't match the target hostname.
The question is whether there is something else I haven't taken into account that will force me to buy more expensive type of subscription? Maybe some specific requirenments from Google that basic subscription can't work with.
Basic $5 subscription works perfectly. It fits all Google's requirements + it provides static URLs that make it possible to receive PUSH notifications even when you restart your ngrok or computer.
I have a Web Client and a Web Api running on the same server which are both set up as separate applications under the common IIS default website. The website is configured with two https bindings, one for each app. The Web Client talks to the Api.
Now to my problem. I can't get https to work. When I specify that the Web Client should access the Web Api over https I get get an error while accessing the Web Api from my machine over https works fine.
Web Client (app server) -> Web Api (app server)
ok: http://"server name"/webapi/
not ok: https://"server name"/webapi/
not ok: http://"host name"/webapi/
not ok: https://"host name"/webapi/
Web Client (my machine) -> Web Api (app server)
ok: http://"server name"/webapi/
not ok: https://"server name"/webapi/
ok: http://"host name"/webapi/
ok: https://"host name"/webapi/
Also, both sites are configured to use windows authentication.
The problem seems to have been that I was using an alias as "host name" which for some reason won't work in this scenario. Calling the Web API using alias from another machine works fine but not between the Web client and Web API on the same server. Changing "host name" to full computer name together with creating a matching certificate solved it.
I think your problem might be with the Double-Hop Authentication issue. Refer to these links for information and a potential solution:
ASP.NET Web Blog about the issue
Steps to get around the issue
Without an actual error code (502, 403, etc.) it's hard to determine what the actual issue might be. One other thing might be if you are using a self-signed SSL cert you may have to manually allow the application to connect to the website with an invalid/self-signed cert, as you indicated it works without HTTPS (or so I read it as).
I'm the one who is configuring the server. It has a SVN+SSH as well as an SSL for the company who will be accessing it. I am able to browse AND checkout repos. The firewall has been configured to allow access to another company. They can browse the repos in a browser, but they get an error message when trying to SVN check-out the repo. Error message: "Access to 'https://servernameaddress/path/to/repo' forbidden". Why would they be able to browse the repo in a web browser, but not be able to checkout using an SVN client?
Are they connecting to the internet via a proxy?
If they had a proxy configured in the browser perhaps Tortoise is not using this proxy.