Latest Contributions by JonathanQuinn

If you're using a self signed certificate, no browser is going to trust the certificate by default. You need to import the certificate into the trusted root authority store to force the OS to trust the certificate. Yes, the idea is that the certificate will be created for the FQDN where the AEB is being installed on. The SSL certificate parameter is just the name of the certificate, it doesn't need to match the FQDN it's assigned to. It could be "myCert", doesn't matter. ... View more

Q1: I think a big part about managing certificates for load balancers is the type of load balancing you're doing, layer 4 vs layer 7. If you're using layer 4, then the certificate you use needs to have SANs for the LB as well as all backend machines, since you're not decrpyting the trarffic at the LB. On the other hand, a layer 7 LB must be able to inspect the traffic to know where to send the request. The certificate on the LB can be different from the certificates used by the backend machines, which can remain as the self-signed certificate, (or any domain certificate you want to use). Q2: Yes, ArcGIS Enterprise can function in an environment where there are multiple NICs, but the changes described below have to be done prior to configuring the environment: Configure ArcGIS Server in advanced scenarios—Deploy | ArcGIS Enterprise  Installing Portal for ArcGIS—Portal for ArcGIS (10.7 and 10.7.1) | ArcGIS Enterprise  Create a data store—ArcGIS Data Store (Windows) Installation Guide | ArcGIS Enterprise  If you already have an existing deployment, then you may have trouble adding that second private IP and configuring Enterprise to use it. Q3: I don't suggest copying files/folders around as a backup/recovery or disaster recovery plan. That workflow isn't technically support by Support Services so any issues that may come up after doing so may not be fixable. Which is a good lead in to: Q4: The documentation on disaster recovery, (taking a backup from one environment and restoring to another), using the WebGIS DR tool is here. The documentation on what must be the same between primary and standby deployments are documented here. Did you use the AWS CF templates to create the site? If so, those add etc\hosts entries to the machines, so the public URL resolves to the local IP when you're on the machine. This makes it easy to set up a new environment because you don't need to worry about traffic getting sent to your primary environment during a restore. ... View more

Those types of errors are challenging to troubleshoot without Supports help. You can try again with server logging DEBUG logs but you may want to reach out to Support for further assistance. If you do, have them log a bug to improve on that error. ... View more

When printing, the machine hosting the printing tools used in the web application is making an outbound request to all URLs in your web application/webmap. It sounds like your ArcGIS Server machine doesn't have access to the URLs that are being printed, likely due to a firewall. On the Server machine, see if you can reach the REST endpoint in a browser: Imagery/Orthoimagery_Latest (ImageServer)  If not, printing that service won't work. ... View more

It seems like it didn't work, but I've never experienced that on my end. Does your machine have multiple NICs? All of that aside, best practice is to have the components, (Portal, Server, and Data Store) on an internal network network that is isolated via a firewall. Within your DMZ you'll have a web adaptor or reverse proxy to send requests to the backend servers. Putting everything on one machine that is accessible by the internet is definitely not typical for a production or public facing system. ... View more

This is fixed at 10.8. The problem is the connection to the license information on the new primary/original standby becomes stale after a failover. Stopping standby and restarting the current primary would fix it. During a restore, the portals restart it makes sense that it would go away after a restore. ... View more

Yes, if you flip your proxy server to point to the new environment, there's no need for etc\hosts entries. The point of the etc\hosts entries is so you can configure the environment without affecting your primary/production environment. If you can accept some downtime, that's not necessary. ... View more

It's possible if you set up a SplitDNS type approach. Public users are routed to an external entry point, (https://portal.domain.com/portal) that's configured with anonymous access, while internal users are routed to an internal entry point with the same FQDN (https://portal.domain.com/portal). This entry point is configured with IWA. Aside from that, SAML is your best bet. ... View more

Do you recall the problem or error when you were restoring Portal? Did you reach out to technical support for troubleshooting? ... View more

No, it's not and I haven't heard of a situation where one of the machines will lose a certificate outside of an administrator deleting it. Are you using chef to deploy the environment? ... View more

The certificates within a highly available portal are maintained separately on each portal machine. The sslCertificates API can return different certificates depending on if you've imported different certificates to each machine. Each machine should trust root or intermediate certificates in any certificate chain that Portal is making requests to: Configuring the portal to trust certificates from your certifying authority—Portal for ArcGIS (10.7 and 10.7.1) | ArcG…  ... View more

Check the logs, they may tell you why the index service can't start: C:\Program Files\ArcGIS\Portal\framework\runtime\ds\usr\logs\<machine>\elasticlog\bds_<id>.log ... View more

I tried this on my side, not too sure why it expects it to be an Online organization when the docs indicate it can be an ArcGIS Enterprise deployment: Might want to reach out to tech support or create an issue in the arcgis-python-api repo to see what's going on. ... View more