I used the microservice template and i keep having same issues - Template: microservice
- Created ABP Studio Version: 1.1.2
- Current ABP Studio Version: 1.1.2
- Multi-Tenancy: No
- UI Framework: mvc
- Theme: leptonx
- Theme Style: system
- Theme Menu Placement: side
- Run Install Libs: Yes
- Database Provider: ef
- Database Management System: sqlserver
- Mobile Framework: none
- Public Website: No
- Social Login: No
- Include Tests: Yes
- Dynamic Localization: No
- Kubernetes Configuration: Yes
- Grafana Dashboard: Yes
- Use Local References: No
- Optional Modules:
- FileManagement
- TextTemplateManagement
- AuditLogging
- OpenIddictAdmin
- Selected Languages: English
- Default Language: English
- Create Command: abp new EPSPlusPay -t microservice --ui-framework mvc --database-provider ef --database-management-system sqlserver --theme leptonx --skip-migrator --without-cms-kit --dont-run-bundling --no-social-logins -no-saas -no-gdpr -no-language-management -file-management
1 Answer(s)
-
0
The error message in your screenshot,
System.OperationCanceledException
with a stack trace involvingStackExchange.Redis.RedisCache.GetAsync
, indicates that your services are unable to connect to the Redis server. This is a common issue in ABP microservice solutions, as Redis is used for distributed caching and data protection.In the ABP microservice template, Redis is a required dependency. If Redis is not running, misconfigured, or unreachable, you will see these types of exceptions and your services may fail to start.
How to resolve:
Ensure Redis is running:
- If you are using Docker, make sure the Redis container is up and accessible.
- If you are running Redis locally, verify it is running on the expected port (default: 6379).
Check your connection string:
- Open your
appsettings.json
or environment variables and verify theRedis
connection string is correct for your environment. - Example:
- Open your
"Redis": { "Configuration": "localhost:6379" }
Kubernetes/Containerized environments:
- If you are running in Kubernetes, ensure the Redis service is deployed and the DNS name in your configuration matches the service name in your cluster.
Restart your services:
- After fixing Redis, restart all your microservices to ensure they can connect.
Check for other dependencies:
- The microservice template also requires SQL Server and other infrastructure services. Make sure all required services are running and accessible.
Sources:
This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.