updates

UPDATED_RESTART_INSTRUCTIONS.md

@@ -44,3 +44,26 @@ Configuration complete; ready for start up
 ### 5. If api-nginx Still Shows Issues
 
 Check if PHP-FPM is running in the API container:
+1. Go to the `opnform-api` container
+2. Check the logs - should show: `fpm is running, pid 1`
+3. If PHP-FPM isn't running, the API container needs to be restarted
+
+### 6. Common Issues
+
+**Port already in use:**
+- Make sure no other services are using ports 7654 or 7655
+- Check with: `netstat -tlnp | grep -E '7654|7655'` on the host
+
+**Cannot connect to API:**
+- Ensure firewall allows ports 7654 and 7655
+- Try accessing locally first: `curl http://localhost:7654/api/health`
+
+**nginx won't start:**
+- Check logs for configuration errors
+- Verify the api-nginx.conf file exists
+
+## Security Reminder
+Services are now exposed on all network interfaces (0.0.0.0). For production:
+- Configure firewall rules to restrict access
+- Set up your host nginx with SSL as planned
+- Or change back to 127.0.0.1 after testing